But before going into too much depth, make sure the duration isn't just
basically identical to clicking on the "reload block library" button,
which is first IO-bound (which *can* take significant amount of CPU time
on weaker ARMs) and then parsing-limited.
Best Regards,
Marcus
On 9/29/21 11:21 AM, Johannes Demel wrote:
Hi,
I used:
https://docs.python.org/3/library/profile.html#module-cProfile
in the past to locate the problematic lines of code.
```
import cProfile
import pstats
with cProfile.Profile() as pr:
run_the_problematic_function_etc()
stats = pstats.Stats(pr)
stats.sort_stats('cumtime').reverse_order()
stats.print_stats()
```
You might want to adopt these lines for your use-case. I started at
the top-level of my application and then gradually moved the code to a
more fitting function.
Cheers
Johannes
On 28.09.21 23:40, Jameson Collins wrote:
I have a completely blank flowgraph (well just the default 'Options'
block).
On my 8 core, 2 GHz, Intel based virtual machine this flowgraph
generates in under a second.
On my 4 core, 1GHz, embedded ARM processor it takes 56 seconds and
completely maxes out 1 core while it's running.
Why might cause this? How might I troubleshoot it?
