Hi,

> > On the other hand though, it gives me some comfort that the hardware
> > being used in my operation will meet any future needs. We have
> > similar spec servers (P3-1Ghz dual-cpu, 512Mb RAM, 3x36Gb SCSI
> > RAID5). Maybe I should try out mysql-super-smack and see what kind
> > of numbers it turns up. :-)
>
> It would be interesting.

Well, I finally got super-smack compiled and running (had to make a couple
of amendments to die.cc and gen-data.cc - thanks Joshua S), so here are my
results:

# super-smack -d mysql select-key.smack 25 100
Query Barrel Report for client smacker1
connect: max=27ms  min=0ms avg= 7ms from 25 clients
Query_type      num_queries     max_time        min_time        q_per_s
select_index    5000    0       0       8271.83

# super-smack -d mysql update-select.smack 25 100
Query Barrel Report for client smacker
connect: max=20ms  min=0ms avg= 4ms from 25 clients
Query_type      num_queries     max_time        min_time        q_per_s
select_index    2500    1       0       3154.04
update_index    2500    1       0       3154.04

Performance peaks at 25 clients, with performance being lesser with fewer or
greater numbers of connections. I find it strange that performance is
relatively 'poor' with only 1 client (at 5153.31 q/sec) - must probably be
something to do with caching. What's better though, is that performance at
250 clients is just as good as with one!

This was on a machine with the spec. above and running Red Hat 7.0 (kernel
2.2.16-22enterprise) and MySQL 3.23.38 with the following config:

set-variable = max_connections = 500
set-variable = key_buffer=256M
set-variable = join_buffer_size=16M
set-variable = sort_buffer=16M
set-variable = record_buffer=16M
set-variable = tmp_table_size=64M
set-variable = table_cache=256
set-variable = thread_cache_size=16
set-variable = thread_concurrency=4
set-variable = back_log=100
set-variable = max_allowed_packet=2M
set-variable = wait_timeout=240
skip-locking

Regards,

Basil Hussain
---------------------------------------
Internet Developer, Kodak Weddings
E-Mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to