If you're using only MyISAM tables for your data, then key_buffer should generally have as much RAM as it can have (up to the point where it makes sense, i.e., only has much RAM as is needed to store your index data). myisam_sort_buffer_size ought to be about 1/4 of your RAM.
I re-ran the benchmarks with a 'tuned' my.cnf (much more memory for various variables). It looks to me like there is no significant difference in the results.
I checked (with phpmyadmin, MySQL system variables) if the new my.cnf was actually being used: it was.
JP
New my.cnf + benchmark results: ==============================
set-variable = key_buffer=512M set-variable = max_allowed_packet=1M set-variable = table_cache=1024 set-variable = sort_buffer=8M set-variable = net_buffer_length=32K set-variable = record_buffer=8M set-variable = thread_cache=8 set-variable = myisam_sort_buffer_size=256M
alter-table: Total time: 181 wallclock secs ( 0.21 usr 0.05 sys + 0.00 cusr 0.00 csys = 0.26 CPU)
ATIS: Total time: 63 wallclock secs ( 5.06 usr 6.26 sys + 0.00 cusr 0.00 csys = 11.32 CPU)
big-tables: Total time: 55 wallclock secs ( 6.60 usr 14.08 sys + 0.00 cusr 0.00 csys = 20.68 CPU)
connect: Total time: 235 wallclock secs (36.76 usr 37.77 sys + 0.00 cusr 0.00 csys = 74.53 CPU)
create: Total time: 287 wallclock secs ( 7.25 usr 2.56 sys + 0.00 cusr 0.00 csys = 9.81 CPU)
insert: Total time: 3018 wallclock secs (415.53 usr 260.06 sys + 0.00 cusr 0.00 csys = 675.59 CPU)
select: Total time: 1371 wallclock secs (46.60 usr 23.62 sys + 0.00 cusr 0.00 csys = 70.22 CPU)
transactions: Test skipped because the database doesn't support transactions
wisconsin: Total time: 25 wallclock secs ( 2.67 usr 2.41 sys + 0.00 cusr 0.00 csys = 5.08 CPU)
Old my.cnf + benchmark results: ==============================
set-variable = key_buffer=64M set-variable = max_allowed_packet=1M set-variable = table_cache=256 set-variable = sort_buffer=4M set-variable = net_buffer_length=8K set-variable = record_buffer=1M set-variable = thread_cache=8 set-variable = myisam_sort_buffer_size=8M
alter-table: Total time: 141 wallclock secs ( 0.22 usr 0.11 sys + 0.00 cusr 0.00 csys = 0.33 CPU)
ATIS: Total time: 59 wallclock secs (10.59 usr 6.30 sys + 0.00 cusr 0.00 csys = 16.89 CPU)
big-tables: Total time: 57 wallclock secs ( 7.53 usr 13.50 sys + 0.00 cusr 0.00 csys = 21.03 CPU)
connect: Total time: 252 wallclock secs (44.31 usr 38.81 sys + 0.00 cusr 0.00 csys = 83.12 CPU)
create: Total time: 298 wallclock secs ( 8.76 usr 3.06 sys + 0.00 cusr 0.00 csys = 11.82 CPU)
insert: Total time: 3316 wallclock secs (594.82 usr 261.66 sys + 0.00 cusr 0.00 csys = 856.48 CPU)
select: Total time: 1428 wallclock secs (67.50 usr 25.18 sys + 0.00 cusr 0.00 csys = 92.68 CPU)
transactions: Test skipped because the database doesn't support transactions
wisconsin: Total time: 27 wallclock secs ( 4.19 usr 2.58 sys + 0.00 cusr 0.00 csys = 6.77 CPU)
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
