# Perspective Script Execution Profiler & Analysis Suite **URL:** \ **Category:** Ignition Exchange\ **Tags:** scripting, perspective\ **Created:** [October 23, 2026, 12:33am UTC](https://forum.inductiveautomation.com/t/perspective-script-execution-profiler-analysis-suite/117581 "2026-10-23T00:33:56Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 23, 2026, 12:38pm UTC](https://forum.inductiveautomation.com/t/perspective-script-execution-profiler-analysis-suite/117581/5 "2026-10-23T12:38:05Z")
Importing `system` at the top level of a library script is unnecessary but harmless--a tiny bit of wasted time. Importing **across** project library scripts is _ **dangerous** _, particularly in v8.1 and older. Mainly because of this longstanding bug: > [@\[IGN-6503\]Project Library Script Initialization Races](https://forum.inductiveautomation.com/t/ign-6503-project-library-script-initialization-races/98636/1): > > Are you annoyed by pseudo-random breakage in Ignition project library scripting? Odd top-level constants being garbled, or operations in the top level that have side effects running twice? Or more? Not happening much, but always around project edits, and sometimes even on gateway restart? Yeah, me too. frowning_face Poking around under the hood back in the spring, for a module development task, I ran across some problematic IA bytecode and pinged some people. But it went nowhere, as I co… This extension is actively promoting importing `profiler`, where it should be directing users to reference the fully-qualified `scriptProfiler.profiler` everywhere. --- _[View the full topic](https://forum.inductiveautomation.com/t/perspective-script-execution-profiler-analysis-suite/117581)._