is it faster now?
the settings below was also important, i tried only to split because i
was not sure which version you are using
Oh yes, big improvement!
18577 msgs (560MB) imported in:
real 107m55.162s
user 1m57.277s
sys 0m16.965s
That's about 1/4th to 1/3rd the times in all of my MySQL testing.
The key was shifting the memory cache allocations to the innodb section
of things rather than the top part of [mysqld].
My my.cnf:
skip-external-locking
key_buffer_size = 96M
max_allowed_packet = 16M
table_open_cache = 256
sort_buffer_size = 32M
read_buffer_size = 32M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 128M
thread_cache_size = 8
query_cache_size= 64M
thread_concurrency = 4
innodb_data_file_path = ibdata1:500M:autoextend
innodb_log_group_home_dir = /mail/db
innodb_buffer_pool_size = 1024M
innodb_additional_mem_pool_size = 64M
innodb_log_file_size = 512M
innodb_log_buffer_size = 256M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
innodb_buffer_pool_size = 1024M
innodb_buffer_pool_instances = 5
innodb_purge_threads = 1
innodb_max_purge_lag = 200000
innodb_thread_concurrency = 32
innodb_thread_sleep_delay = 10
innodb_read_io_threads = 8
innodb_write_io_threads = 8
transaction-isolation = READ-COMMITTED
My server is running a "Linux Generic x86" build: mysql-5.5.15-linux2.6-i686
yes, with a lot of optimizing for Core2 and SSE 4.1, -O6 and so on
Sounds what I prefer to do when I can... :(
At times, the Gentoo portage system is very appealing, but they lack a
MySQL 5.5 ebuild that's stable.
i read docs too, but i like it more to optimize the builds of my distribution
because
they usually knwoing what they are doing and including often a lot of patches,
many of
them for the build-process depending on the current GCC version
Hrm, maybe I should try to refactor an SRPM to do it for my Slackware
systems.
boah do not do this in production
below my mount-options and i thought they are a little on the dark side :-)
Yes, I know it's risky, but for "flat out" performance testing just to
see where the really hard corner edge cases are, I was getting desperate.
"barrier=0" is ok here because there are two UPS sytems and the SAN-Storage
is battery backed too, means the buffers are safe at every time
Yeah, I would agree with your reasoning here. With BBU-backed RAID,
it's probably safe to disregard write barriers.
Thank you for your help, Reindl. You've been very generous with your
time and attention, and I appreciate it.
=R=
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
