Device adding/deep refresh speed reduced in Jajuk 1.8

[louie55]

This ticket is for the discussion of the fact that the speed of adding a device or performing a deep refresh has been reduced in Jajuk 1.8. At least on some computers.

I performed a benchmark on a collection with 6643 songs in 457 albums.

My computer has 3GB of RAM and a P4 3.4 GHz CPU.

I did some benchmarking between adding that same large collection on 1.7.4 and 1.8dev_20090722. I did it multiple times on each under the same computer conditions. My results show that on my computer, 1.8dev takes roughly twice as long to add the collection as 1.7.4. Here are my refresh times for the 3 runs I did on each:

1.7.4: 22 Seconds, 21 Seconds, 17 Seconds
1.8dev: 44 Seconds, 52 Seconds, 44 Seconds

So refresh speed has been slown down. However, 44 seconds for a large collection still isn't too bad. So it would be up to the developers to decide if this is acceptable.

Have kept this ticket as "Discussion" type for now.

[bflorat]

OK, This may be a cache issue. I have to check this again. For a very large collection on a NAS, I didn't observe such difference.

If I understand well, the times you provide are run time average each among 3 launches, right ?

[bflorat]

Update : a new benchmark on a large collection located on an USB drive (in secs) :

• jajuk 1.7 : 478, 370, 369
• jajuk 1.8 : 587, 375, 377

Seems that jajuk 1.8 and 1.7 have same refresh time for me on NAS and USB drive. Where is located your collection ? on the internal hard disk ?

[louie55]

What I did for the tests is install Jajuk fresh, then ran the device add. That is the first time listed. Then, in the "Files" view, I removed the device and then added the device again using the device wizard. In total, I refreshed each 3 times. In fact, before performing these tests, on my first import with 1.8, it took 127 Seconds. Not sure why it took so long that first time. The times I list are the times that are displayed by Jajuk after it is done refreshing.

My collection is located on an internal SATA Hard Drive (on a logicial partition). The partition has 37GB of free space. The music is on the same physical drive as the Operating System, but on a separate partition. The total size for all of the music being added is 30.3 GB. There are in total, 654 folders and each has it's own folder.jpg album art file. All are MP3 files, both CBR and VBR. OS is Windows XP Pro SP3.

Even while watching it refresh you can see a noticeable difference in how long it displays each folder while it is refreshing. In 1.7 it zooms through the folders so that you can barely read what it says. In 1.8 the folder names flash by much slower.

[anonymous]

Not sure why it took so long that first time. The times I list are the times that are displayed by Jajuk after it is done refreshing.

I think it's because of the the hardware and OS cache fill-up. That's why in our benchmarks, the first is unsignificant.

There are in total, 654 folders and each has it's own folder.jpg album art file. All are MP3 files, both CBR and VBR. OS is Windows XP Pro SP3.

The pictures have no effect during refreshing, only tracks and playlists are scanned.

Even while watching it refresh you can see a noticeable difference in how long it displays each folder while it is refreshing. In 1.7 it zooms through the folders so that you can barely read what it says. In 1.8 the folder names flash by much slower.

That's part of my last fix, we only refresh GUI every 100 ms to save CPU (BTW, we should perhaps set 50 ms)...