Comments on: DB changes — call for benchmarkers!

By: redm

redm — Tue, 21 Jul 2009 19:31:40 +0000

Better late than never…

(I tested against 2.1.1, as recompiling amarok takes ages on this machine…)

2.1.1:
1st: 1min 50s
2nd: it went weird when I treid that…

SVN:
1st: 1min 29s
2nd: 0min 56s

So not bad I’d say… This is with about 3400 tracks. And CPU was always at 100%.

By: jefferai

jefferai — Mon, 20 Jul 2009 15:18:23 +0000

You mean http://amarok.kde.org/blog/archives/1067-MySQL-Server-Support-Promised-and-Delivered.html ?

By: Jessie Morris

Jessie Morris — Mon, 20 Jul 2009 07:39:57 +0000

Is there ever going to be plans for having a full MySQL server in use with Amarok? Are there any huge technological problems as to why this can’t happen? Obviously don’t make it the default, but allowing it would certainly be nice!

By: redm

redm — Sat, 18 Jul 2009 20:47:21 +0000

Err, wrong thread. That was about MySQL Embedded, of course…

By: redm

redm — Sat, 18 Jul 2009 20:45:42 +0000

Ah, that’s what I was looking for! Thanks! I added it to the overview list on http://amarok.kde.org/wiki/Development. Hope that’s ok.

By: jefferai

jefferai — Sat, 18 Jul 2009 15:52:56 +0000

Yep…see the bottom of this page:

http://amarok.kde.org/wiki/Development/MySQL_Embedded

By: jefferai

jefferai — Sat, 18 Jul 2009 15:46:21 +0000

Thanks for doing this! Glad you got a nice speedup.

By: jefferai

jefferai — Sat, 18 Jul 2009 15:45:05 +0000

Glad you got a nice speedup. Based on the other user above and Nikolaj’s experience, if you tested it with caching it’d have been even more massive

Thanks for the results!

By: redm

redm — Sat, 18 Jul 2009 15:14:02 +0000

Btw.: Is there a tool which I can use to browse the MySQLe databases? Or dumping to a formatted textfile? I couldn’t find anything useful, as most tools are only for real MySQL servers…

By: Mikko

Mikko — Sat, 18 Jul 2009 12:43:42 +0000

Ok, so I decided to try this better and I found out there’s indeed a speed increase, but I didn’t try step 5 with caching.

In older revisions the total scan time was split in two parts:
- Real scanning (disk activity, changing entries in collection_scan.log)
- Something else, I guess like building the actual database or initializing, etc..

rev 995000:
- 1st part: 11 min 40 sec
- 2nd part: 2 min
TOTAL: 13 min 40 sec
http://i25.tinypic.com/rqw4nc.png

In trunk the second part is totally gone
The first part *is* the whole scan:
- 1st part: 11 min 36 sec
TOTAL: 11 min 36 sec
http://i28.tinypic.com/2qvr1ux.png

And another improvement is cpu usage,
you can clearly see how it was before and after the upgrade.

Overall it’s a 15% speedup
Thanks Jeff.

By: Kuba

Sat, 18 Jul 2009 01:53:53 +0000

Here’s what I got:

r995000:
1st time: 137s //and it crashed at 100%
2nd time: 76s

r998526
1st time: 122s
2nd time: 33s

Really big improvement, Thanks and congratulations Jeff!