PDA

View Full Version : very slow response time when browsing genres



wotuzu17
2007-07-13, 11:19
Hi,

I just upgraded Slimserver 6.3 to 6.5.3, using the Suse10.1 system's mysql server.
My Server is a VIA C3 / 1Ghz 256MB

my music consists of 1400 albums with 18434 songs by 560 artists.

Basically everything works fine so far, only when I browse my music for genres, the cpu load goes to 100% for minutes. When I check the top command, I see that mysqld is using all the CPU power.

For example, when I click on the rock genre, which contains 642 albums, I need to wait 6 minutes for a reaction. In the meantime, the music on my squeezebox stops due to the heavy cpu load.

The old version 6.3 needed 5 seconds for the same request.

Interestingly, browsing via the IR Control Search->Genres->Rock is going very fast.

I already experimented with increasing buffer values in /etc/my.cnf, but that doesn't help much.

I'd be happy for comments, especially from Michael since he seems to use the same hardware as I do.

wotuzu17
2007-07-13, 11:23
Here are the relevant settings in /etc/my.cnf:

[mysqld]
innodb
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
innodb_fast_shutdown = 1
max_connections = 4
thread_concurrency = 4
key_buffer = 32M
max_allowed_packet = 1M
table_cache = 256
sort_buffer_size = 2M
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 16M
[...]
# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /var/lib/mysql/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /var/lib/mysql/
innodb_log_arch_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 32M
innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
[...]

wotuzu17
2007-07-13, 12:14
I'd like to add that all other ways of browsing are AMAZINGLY FAST. Way faster than at my 6.3 installation. Only broswing for genres that contains lots of albums in my database like Rock and Pop take INSANELY long time.

Therefore I assume that it is not about my relatively weak hardware, nor about the setup of the mysql server, but a inefficient way of querying the server for genres, that results in high CPU load and that ludicrous response times.

How does your slimserver6.5.3 installation react?

I use the workaround of browsing for Music Folders, since my folders are organized in Genres.