Slow start with custom userprefs #82424

Closed
opened 2020-11-05 10:09:00 +01:00 by Benoit Alexis · 12 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77

Blender Version
Broken: version: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: blender/blender@3e85bb34d0
Worked: (newest version of Blender that worked as expected)

Short description of error
Using the blender cloud addon I sync my userprefs across multiple computers. However when I do this, blender takes a solid 30 seconds to start.

Exact steps for others to reproduce the error
When deleting the userprefs folder blender starts in a few seconds, however when I sync the userprefs using the blender cloud addon it is really slow again.
I have deleted the startup file, disabled the blender cloud addon (which is the only "custom" addon) but it takes as long, so the problem must be elsewhere...
Here is my AppData/Roaming/BlenderFoundation/ prefs folder
2.90.zip

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77 **Blender Version** Broken: version: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: `blender/blender@3e85bb34d0` Worked: (newest version of Blender that worked as expected) **Short description of error** Using the blender cloud addon I sync my userprefs across multiple computers. However when I do this, blender takes a solid 30 seconds to start. **Exact steps for others to reproduce the error** When deleting the userprefs folder blender starts in a few seconds, however when I sync the userprefs using the blender cloud addon it is really slow again. I have deleted the startup file, disabled the blender cloud addon (which is the only "custom" addon) but it takes as long, so the problem must be elsewhere... Here is my AppData/Roaming/BlenderFoundation/ prefs folder [2.90.zip](https://archive.blender.org/developer/F9206461/2.90.zip)
Author

Added subscriber: @BenoitAlexis

Added subscriber: @BenoitAlexis

Added subscribers: @dr.sybren, @mano-wii

Added subscribers: @dr.sybren, @mano-wii

@dr.sybren, if I'm not mistaken, you are one of the authors of the blender cloud addon.
30 seconds is a long time.
Perhaps, the addon did not expect the user preference to be shared between multiple computers.
But I'm not sure if the problem is with the addon or something specific in the Windows I/O System.

@dr.sybren, if I'm not mistaken, you are one of the authors of the blender cloud addon. 30 seconds is a long time. Perhaps, the addon did not expect the user preference to be shared between multiple computers. But I'm not sure if the problem is with the addon or something specific in the Windows I/O System.
Author

I did a few tests :
I was initially using Blender Launcher, so I deleted all my installs and started fresh with the installer off blender.org
It takes roughly 20-25 seconds to start the first time. I close, start again, it's instantaneous.
(When I say it takes 20 seconds, a blank, light gray, full screen blender window opens with the rotating cursor.)
I install the blender cloud addon, login, load the preferences, close.
Almost a whole minute to start it again.
Disable the addons, remove the user prefs folder, close, 25 seconds to start.
Close, re open : instantaneous.
Close, re open : 25 seconds.
I change a few keymaps to regenerate a userprefs file, close re open : 25 seconds...
Is there a log somewhere that might show what is happening ? The system console is empty apart from :

Read prefs: C:\Users\SHOWROOM\AppData\Roaming\Blender Foundation\Blender\2.90\config\userpref.blend
found bundled python: C:\Program Files\Blender Foundation\Blender 2.90\2.90\python 

I get the same behaviour with the portable version.
It takes 70 seconds to start the first time. But if I close it without changing anything, the next start takes 2 seconds. I have tried 4 times : open/close without change, always 2 seconds. But if I delete the cube and add a monkey, the next start will take again 20 seconds.
Now 20 seconds is not really a long time compared to other software but I recall Blender being very fast to load empty scenes, is this from new versions ? I don't think the hardware i'm using can be the culprit (i9, 32GB, 2080ti)

I did a few tests : I was initially using Blender Launcher, so I deleted all my installs and started fresh with the installer off blender.org It takes roughly 20-25 seconds to start the first time. I close, start again, it's instantaneous. (When I say it takes 20 seconds, a blank, light gray, full screen blender window opens with the rotating cursor.) I install the blender cloud addon, login, load the preferences, close. Almost a whole minute to start it again. Disable the addons, remove the user prefs folder, close, 25 seconds to start. Close, re open : instantaneous. Close, re open : 25 seconds. I change a few keymaps to regenerate a userprefs file, close re open : 25 seconds... Is there a log somewhere that might show what is happening ? The system console is empty apart from : ``` Read prefs: C:\Users\SHOWROOM\AppData\Roaming\Blender Foundation\Blender\2.90\config\userpref.blend found bundled python: C:\Program Files\Blender Foundation\Blender 2.90\2.90\python ``` I get the same behaviour with the portable version. It takes 70 seconds to start the first time. But if I close it without changing anything, the next start takes 2 seconds. I have tried 4 times : open/close without change, always 2 seconds. But if I delete the cube and add a monkey, the next start will take again 20 seconds. Now 20 seconds is not really a long time compared to other software but I recall Blender being very fast to load empty scenes, is this from new versions ? I don't think the hardware i'm using can be the culprit (i9, 32GB, 2080ti)
Author

I just figured something out : Launching blender with administrators rights makes it start much faster. I tested both with the installed version and the portable one.
I'll just do this for now...

I just figured something out : Launching blender with administrators rights makes it start much faster. I tested both with the installed version and the portable one. I'll just do this for now...
Author

Alright I found the culprit. After taking the computer home from work, I still had a network drive that couldn't be accessed. It was also causing explorer to freeze randomly from time to time.
Disconnecting the drive for good (took a while, even a right click on the drive was causing explorer to freeze for a solid 30 seconds), blender is now faster to launch than explorer.
I am still curious as to why starting blender as administrator was somehow bypassing the issue ?

Alright I found the culprit. After taking the computer home from work, I still had a network drive that couldn't be accessed. It was also causing explorer to freeze randomly from time to time. Disconnecting the drive for good (took a while, even a right click on the drive was causing explorer to freeze for a solid 30 seconds), blender is now faster to launch than explorer. I am still curious as to why starting blender as administrator was somehow bypassing the issue ?
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

@BenoitAlexis Do I understand correctly that the issue is not specific to Blender and also happens for the native file explorer due to that faulty drive? Do you still think that this is an issue that Blender need to handle?

@BenoitAlexis Do I understand correctly that the issue is not specific to Blender and also happens for the native file explorer due to that faulty drive? Do you still think that this is an issue that Blender need to handle?
Author

No my guess is that this is caused by how Windows handles disconnected network drives. So it depends if there is a way to shorten the timeout within blender for these drives, or flag them as "unreachable" the first time it fails to connect, and let the user know that further attempts to reach these drives will be ignored, to speed up the whole I/O UX... But this sounds like something Microsoft should be handling in the first place, not Blender...

No my guess is that this is caused by how Windows handles disconnected network drives. So it depends if there is a way to shorten the timeout within blender for these drives, or flag them as "unreachable" the first time it fails to connect, and let the user know that further attempts to reach these drives will be ignored, to speed up the whole I/O UX... But this sounds like something Microsoft should be handling in the first place, not Blender... ```
Member

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'
Member

Closed as duplicate of blender/blender#85689

Closed as duplicate of blender/blender#85689
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#82424
No description provided.