Location-specific load times

[dave]

i can only imagine that this is VM related
it does not seem to be something that kJams is doing

[DeusExMachina]

Well, FWIW, I just have the one swapfile0, so it is not like the OS is paging like crazy.

[dave]

so, have you sent me a log file from one of those "five minute load time" runs?

[DeusExMachina]

Yes, several.

[dave]

okay, let's keep working on this offline, and i'll come back here and post our results

[DeusExMachina]

Was there a rogue?

[dave]

yes, in the directory listing folder

[DeusExMachina]

Between 1:20 and 1:50 through loading Playlists.

[dave]

do you have an SSD for the HD on which the Library resides?

[DeusExMachina]

Yes and no. On one machine, it is standard 500 GB drive. This is machine with long load times, including the new 1:20 and 1:50 values. The other machine has a 750 hybrid drive (750 standard HDD and 8GB SSD) where the most used files and blocks are moved to the SSD portion. This machine has much faster load times, but not sure that is due to the drive.

[dave]

i'm going to guess that the long load times happen right after restart, then if you quit (successfully) and run again, it will be faster? in that case the OS has cached much of the disk access already, but if you crash and restart, the cache is purged causing a long load time? but if you're on SSD, the load times are fast, cuz SSD is fast?

if you have gobs of RAM, try moving your "kJams Library" to a RAM disk (which is backed by an HD, of course). see if loading that makes the load time cut down?