VS startup time
-
@861475_VctSt Yet another suspect for the slowdown: there might be too many files in the temporary files folder.
This folder unfortunately is hidden in MacOS and it is different per system.VectorStyler scans the content of this folder for files that might have been created in previous runs (in case of crashes) to avoid accumulating such files.
-
Temporary files are about this.
/private/tmp
With VS ver. 1.0.062 it starts up in 7 seconds, but with ver. 1.0.005 and later it takes about 90 seconds.
Then I would think, in layman's terms, that there must have been something between these versions "regarding startup". What do you think?Of course, I'm thinking "maybe it's time for Catalina to retire".
-
@861475_VctSt said in VS startup time:
been something between these versions "regarding startup". What do you think?
Yes that would be a correct assumption.
But I also tested both 1.2016 and 1.1062 on a MacBook Mid 2012 with Catalina on it. And both start up around 7 seconds.
So I suspect that there might be something here that can be fixed.
BTW: that temp folder is not the one used by apps (temp folders are served by MacOS, and have long /generated names). -
Thanks for all your help and research.
I logged in as a different user and started VS1.2 in 7 seconds.
There seems to be a problem with the main account library.
For now, I will continue to use it as is.Just to be sure, I did the following maintenance on the main account.
Still, the VS startup time did not change.Deleted the cache here. ( /Users/hara/Library/Caches/TemporaryItems )
Rebuilt the Spotlight data.Thanks
-
@861475_VctSt said in VS startup time:
Deleted the cache here. ( /Users/hara/Library/Caches/TemporaryItems )
Rebuilt the Spotlight data.None of these are the problem. The temp folder for apps in MacOS are given by an API called "NSTemporaryDirectory"
For me this is: /var/folders/05/z_3lq3qx1r3fwq25d68vr6g00000gp/T/
But a lot of other apps place their data in this folder.
If the content of the folder is too large then VS startup may take longer. -
/private/var/folders/6y ( mk, nt, zz )
I manually removed one by one the 0 capacity folders in each of the 6y, mk, nt, and zz folders.
Not all were deleted, but quite a few were reduced.
The ones in zz are highly dangerous, so I backed up and deleted only the ones I thought I could delete.As a result, the rainbow cursor spun up in 55 seconds and VS took 60 seconds to boot up.
I then used TinkerTool Systemu and CleanMyMac to delete as much cache as I could in the mac.
One last question that remains is why only VS 1.1 and above takes so long?
I have over 100 other apps installed and none of them take this long. -
@861475_VctSt said in VS startup time:
One last question that remains is why only VS 1.1 and above takes so long?
I think at some point I added a temp file cleanup for startup to avoid VS temp files to accumulate due to crashes.
This searches the temp folder and removes files that were created by VS.
But this is very easy to disable of course. -
Thank you very much.
Ver. 1.2.018 started up in 7 seconds.
I have spent dozens of hours maintaining the machine by myself to no avail.
I ask for the sake of layman's education, can you tell me what you did to improve it? -
@861475_VctSt said in VS startup time:
can you tell me what you did to improve it?
It does not search for past VS temporary files for cleanup when starting.
-
In ver. 1.2.107 there was always an old cache here.
/private/var/folders/6y/bplb4gnn2w76qclj0bgpf1f80000gn/C/com.vectorstyler/com.apple.metalThat seems to be the temporary being cached.
CleanMy Mac can now also delete it as system junk.
I am now free from the frustration of starting VS.
Thank you so much. -
@VectorStyler Where are the temporary files located in Windows?
Should we manually delete them to maintain a clean system since build 1.2.018 doesn't search them? -
@Harry said in VS startup time:
Where are the temporary files located in Windows?
It is up to the operating system to serve the temporary file locations and this may vary between versions.
VS will still clean the temporary files, but it does so after crashes, and not at startups.
With normal exit, VS will not leave temporary files.
