Start up lag

[blitzmann]

I'm not sure if this is still an issue, but there have been a few reports in the 2.x series of pyfa taking a long time to start up. I'm creating this issue to link the other issues.

If you're experiencing this issue

First, please subscribe to the thread to receive new updates and posts! The subscribe button it to the right.

Attaching log files can help determine where the slow down is taking place. Your logs are found in %userprofile%/.pyfa and end in .log. Find the one that shows longish start up times (each log is time-stamped so it should be easy-ish to find gaps when it starts...). it may be helpful to dump the current log to disk by going to Preferences > Logging > Dump all logs

As I investigate, I may also post in this thread new builds that have additional logging to try to narrow down where the issues lie. it would be helpful to keep an eye on notification for any updates to this thread and provide logs and feedback as I work through this progress.

Thanks!

[Calavoow]

My pyfa has been starting noticeably slower since 2.0. Here are my logs
pyfa-2018-05-31.log

[blitzmann]

Thanks @Calavoow! That log shows about 3 seconds of start up, which isn't too bad and kind of normal. Dump another log if you notice it taking much longer than that :) (unless of course this one as a long startup, and the log just didn't catch it?)

[Calavoow]

Another one, after a fresh start pyfa-2018-06-01.log
Seems like 13 seconds this time

[blitzmann]

Thanks!

I need to put a lot more debugging statements when various thing initialize to try to track down where this is taking a while. I'll try to get you a test build that you can run that should show a lot more granularity

[mosni]

pyfa_debug-2018-06-01.log

here's one of mine, I've been struggling with long startup times for a while

[blitzmann]

I'm attempting something that is either completely clever, or completely crazy

With bb978c3 you should now be able to specify a path to save profiling information. While this introduces additional overhead, as well as possible increased start up times, it will track the function calls within pyfa and allow me to determine what is eating up time. This will save to file in whatever directory you specify, and then you can upload it here for me to analyse.

If you don't specify a profile location, then it works just as it does now, so no overhead

I'll try to get a build out tonight and distribute in this thread for you guys to try this. I'm interested in seeing if it works out. :)

[blitzmann]

greetings all!

If you wouldn't mind, please download this build: https://ufile.io/dpw4a

You should be able to run this with the -p flag: open up command prompt, and run the pyfa.exe like so:

pyfa.exe -p c:\my\path\to\save\profiles

When you do this, pyfa will automatically save a profiled instance to the path you specify, in a file called pyfa-<data>.profile.

What I want you guys to do: start pyfa with that command, and when it loads, immediately close it. I don't want you to do a full on fitting session as that would probably be too much data to parse through. Just open it, wait for it to load, and then close it (or, if you want, go and dump the log as well). If you're able to get a lengthy start up, please upload the .profile file here and I can take a look at it.

Thanks!

[fsufitch]

+1 on this. The development build of 2.x was starting slowly, but I figured that was before it went through the optimizations prior to being published. I was only half right. The published version is faster than the dev version, but still slower than 1.x Pyfa by a wide margin.

@blitzmann your ufile.io download is not working. Neither of the download buttons do anything.

[blitzmann]

your ufile.io download is not working. Neither of the download buttons do anything.

Works for me...

Here's an alternative: https://drive.google.com/file/d/14jrMCMd0wiN37VSobckJVM64Fz7CuIOL/view?usp=sharing

Download icon on top right corner

[fsufitch]

pyfa-20180604_180258.zip

[blitzmann]

Thanks! Will take a look. Can you also post the log file? What kind of delay were you getting?