Why does Sonar take a long time to load file FIRST TIME, then fast after that?

Hi Guys,
 
This is something I meant to ask for a long while now, but kept forgetting to ask:D
 
So as the title says - "Why does Sonar take long time to load file FIRST TIME, then fast after that?"
 
I just tried out loading 3 different files. First time out I get Sonar Not Responding,then eventually they open. So Load one, close it .. same for all three. When I came back to any of the three thereafter, they load way faster from that point, no Not Responding.
 
If I close Sonar at this stage .. then reopen it, all three files still load fast. 
 
It literally is the first time ONLY that gives the not responding and slow file load.
 
SPEC - Dell Inspiron 17 7000 Laptop - Nvidia Card, Core i5, 16GB Ram, 1TB Sata drive - WIN 10 PRO
SPLAT ver - 2017.03
 
And yes I realise I could go buy an SSD drive, but for sake of 1st time only it is not worth it at the moment.
 
Using COMODO AV with all audio folders excluded ..
 
Thoughts? Anyone else notice this? Why does it happen? Any way of changing this so files load 1st time out fast? .. Thanks
 

I saw something similar to this in the past but haven't exerienced it for quite a few updates now. What version of Sonar are you running?

One word: Cache

The first time data loads from your hard disk, as well as loading this in standard ram, your PC also stores as much of that data as it can in much faster ram.  This area of RAM is called Cache.  Every PC has some.  How much cache your PC has depends on your CPU and the sub system configuration.

If you load that data again, you PC will look to see if the data is already in the cache. If it is, then the loading takes place from the much faster cache than from it's standard location. That is why Sonar takes long time to load file first time and then quickly after that.

I know it's a bit of a simplified explanation, but that's the general idea.

This might be relevant.  A few here are also users of Band-in-a-Box.  In their latest version for Windows, they released an update that remarkably sped up the loading time.  Typical loading times went from 45 seconds to 6, an amazing improvement.  I don't know what they did, but it was something besides caching because once the program was loaded three times, each time after that it loaded quickly.  This includes loading right after a cold boot, where caching could not be a factor.  The company decided that loading time was a priority, and changed to code to address it. 

Wibbles
This happens with me.
 
I'd put it down to VST Scan not Sonar.

I have VST Scan OFF.
 
I should say this happens first out when Sonar just loaded. Interestingly when one opens a new file .. adding new VSTs might take about 20 secs to load for each.

Close the file and open a new file and start adding new VSTs there .. they load up good and fast

Im not sure what that has to do with caching? Just loading VSTs, no data on the track.
 

Hey Bristol,
 
Your theory did not work :D
 
I opened SONAR, loaded a new file, added two VSTs .. took about 15 secs each to load.
 
Closed Sonar .. opened again. Loaded same 2 VSTs. They loaded straight away.
 
Closed Sonar .. Opened BLENDER 3D app. Did some 3D work on a cube for about 2 minutes. Closed Blender. Opened Sonar. Opened new file. Same 2 VSTs loaded lightening fast ..
 
BTW - I tried the above on my lesser spec'ed Desktop PC ( Core i3, 8GB Ram, Nvidia, M-Audio Profire ext audio box Firewire )
 
 
 
 

aidanodr
Hey Bristol,
 
Your theory did not work :D
 
I opened SONAR, loaded a new file, added two VSTs .. took about 15 secs each to load.
 
Closed Sonar .. opened again. Loaded same 2 VSTs. They loaded straight away.
 
Closed Sonar .. Opened BLENDER 3D app. Did some 3D work on a cube for about 2 minutes. Closed Blender. Opened Sonar. Opened new file. Same 2 VSTs loaded lightening fast ..
 
BTW - I tried the above on my lesser spec'ed Desktop PC ( Core i3, 8GB Ram, Nvidia, M-Audio Profire ext audio box Firewire )
 
 
 
 

Good on you for at least trying it and following up.
 

AntManB
You can use the Sysinternals tool RAMMap to see which files are still cached even after you close the program.
 
https://technet.microsoft.com/en-us/sysinternals/ff700229.aspx
 
You can also use it to empty the cache (choose "Empty Standby List" from the Empty menu).  I suspect that after doing that it will revert to post boot speeds.
 
Just running a few apps is unlikely to clear much of the cache unless you have very limited RAM or very RAM intensive apps.
 
AMB

Thanks Antman,
 
Tried that - "Empty Standby List" from the Empty menu - YES .. it definitely reverted to slower load.
 
Another thing I tried was open sonar, load new file, load a VST. Closed file. Opened new file agin, loaded vst, as suspected faster.
 
Now closed the file - ran "Empty Standby List" from the Empty menu - And VST reverted to slower load