2013-01-14, 22:53
After creating a shared MySQL DB for different profiles on different XBMC, one thing was still bothering me: the slow response when building the TV Shows or Movies view (selecting it from the main menu). It took about 4-5 seconds on my DualCore Atom (ION2) and 20 seconds on a RaspberryPi. So I did some more research and decided to try to change the MySQL caching settings.
MySQL runs on a Windows Server 2012 system with 16GB RAM, a few RAID0 disk arrays, and one Debian Linux VM. Everything is connected through a gigabit ethernet - so that shouldn't be an issue performance-wise.
I added the folowing parameters to the my.ini file (located in the MySQL program directory on Windows):
and I changed the query-cache-size parameter to:
That is probably too much, but since I have plenty of RAM, I didn't bother finetuning it.
And it speeded things up quite considerable! On the Atom device the time from selecting Movies or TV Shows from the main menu until the Showcase or Bannerplex view showed on the screen, dropped to about 1 second on the Atom device and 3-4 seconds on the RaspberryPi.
MySQL runs on a Windows Server 2012 system with 16GB RAM, a few RAID0 disk arrays, and one Debian Linux VM. Everything is connected through a gigabit ethernet - so that shouldn't be an issue performance-wise.
I added the folowing parameters to the my.ini file (located in the MySQL program directory on Windows):
Code:
query-cache-type = 1
and I changed the query-cache-size parameter to:
Code:
query-cache-size = 40M
That is probably too much, but since I have plenty of RAM, I didn't bother finetuning it.
And it speeded things up quite considerable! On the Atom device the time from selecting Movies or TV Shows from the main menu until the Showcase or Bannerplex view showed on the screen, dropped to about 1 second on the Atom device and 3-4 seconds on the RaspberryPi.