finally
Posted by Ian Holsman
congrats to Stefan Rubner
who won the T2000 this month.
Bye Bye Sunfire
Posted by Ian Holsman
Well.. the time has come.. my Try & Buy period is over.. and it is time to return the machine. It’s going to be picked up today.
It’s a shame that sun hasn’t updated it’s winners page I’m guessing they have got enough marketing exposure from Colm (who interestingly couldn’t even officially participate due to him living in Ireland).
sunfirefan.com gets zyoned.
Posted by Ian Holsman
Admittedly SunFire isn’t as popular as it was when it first started, but it made the perfect candidate to get ‘zyoned‘
The conversion was quite painless, and the old URLs still work, which I thought was important.
in other Django news, Ned Batchelder announced Tabblo a community photo sharing site, and Custard Melt is under active development once again.
Sunfire competition status
Posted by Ian Holsman
I’ve been checking the sun winnners about once a day to see if I have won (or who did) and I noticed a couple of changes. (they could have been there all the time, I’m not sure)
- You can now enter with a T1000, which is a smaller 1U offering. Thankfully it looks like they will allocate 1 machine each (ie.. there are 9 T1000’s and 9 T2000’s on offer, not just 9 machines)
- This line is a bit sucky …
If Sun does not receive a sufficient number of eligible submissions during an Entry Period, Sun may, in its discretion, combine two Entry Periods and consider all of the submissions as having been received during both Entry Periods.
Why am I checking so regularly.. well first off all I’m impatient, but my Try&Buy period is about to expire and don’t want to go to the hassle of shipping it back only to turn around and get it returned to me the next day. (and I definatly don’t want a $AUD13k charge on my credit card)
I’m guessing I haven’t won :-(, as I haven’t got a official email from sun yet. Good luck to whoever won it!
How does MySQL perform on a sunfire?
Posted by Ian Holsman
If you have been reading my previous entries the answer you will think is ‘not bloody well’.
After about 3 days of tuning we doubled the throughput, and got a much nicer picture, outperforming a x86-64 machine by 2.5 times in one case.
Thanks to Luojia Chen (Jenny) from Sun, Peter Zaitsev from Mysql, and Colm MacCárthaigh & Mads Toftum from the ASF.
oh.. the benchmark.. I nearly forgot ;-)
(Oh people..please link to the blog entry, and not the paper itself.. Thanks)
update: people were having issues downloading the PDF. so I placed a mirror of it here
so.. why does mysql run so slowly?
Posted by Ian Holsman
this is the output of
dtrace -n 'pid$target:::entry{ @[probefunc] = count() }'
when I run mysqlslap -c 20 -i 20
pthread_getspecific 365 malloc_internal 377 my_malloc 377 free 378 malloc 378 my_wc_mb_filename 399 my_no_flags_free 420 strmake 444 pthread_self 468 memset 582 alloc_root 630 strmov 651 strlen 655 memcpy 897 mutex_trylock 936 my_pthread_fastmutex_lock 936 mutex_lock 1133 mutex_lock_impl 1133 my_utf8_uni 1365 mutex_unlock 2069
I’m about to prepare a more formal analysis (and benchmark) about this. but in order for me not to compete with colm I’m going to wait until the 24th to submit it.
I switched to using sysbench as I thought there might be a bug in actual mysqlslap code, but it is also showing the same results. those being mysql runs 10x slower on the sunfire than on a linux x86-64 machine.
If you are from sun, mysql, or a apache member, and want to check out the configuration to see how I screwed up, send an email from your @sun.com/@mysql.com/@apache.org email address with a public key and I’ll mail you the IP#/account details (ian at holsman.net).
the machine is only available while I’m awake (I live in Australia so it probably means your nighttime), as I haven’t put it in a colo (until I win it of course) and my ‘server room’ is my walk in robe.
sunfire gets a bit of a slap -- update
Posted by Ian Holsman
ok.. now this is getting stranger.
I have 2 windows open, in one I get
$ mysqlslap --use-threads -psunfire -c 90 -i 500
Benchmark
Average number of seconds to run all queries: 2.180 seconds
Minimum number of seconds to run all queries: 0.779 seconds
Maximum number of seconds to run all queries: 4.497 seconds
Number of clients running queries: 90
Average number of queries per client: 0
and in the other i get
$ mysqlslap --use-threads -psunfire -c 90 -i 500
Benchmark
Average number of seconds to run all queries: 0.012 seconds
Minimum number of seconds to run all queries: 0.002 seconds
Maximum number of seconds to run all queries: 0.015 seconds
Number of clients running queries: 90
Average number of queries per client: 0
same machine, same user-id, same binary. the only difference is that mysql started in the ‘fast’ window.
sunfire gets a bit of a slap
Posted by Ian Holsman
and doesn’t seem to take it too nicely :-(
I decided to install the mysql beta on my laptop (Mac Intel @2G ram and 2GHZdual core) and my sunfire (@8G ram and 16 1GHZ Ultrasparcs).
(I have it installed on a x86-64 box as well, but that machine is busy at the moment)..
so for a quick sanity check I ran mysqlslap to see how it performs.
I chose to simulate a 20 concurrent users
sunfire$ mysqlslap -psunfire -c 20 -i 20
Benchmark
Average number of seconds to run all queries: 1.714 seconds
Minimum number of seconds to run all queries: 0.941 seconds
Maximum number of seconds to run all queries: 2.539 seconds
Number of clients running queries: 20
Average number of queries per client: 0
vs
laptop$ mysqlslap -i 20 -c 20
Benchmark
Average number of seconds to run all queries: 1.201 seconds
Minimum number of seconds to run all queries: 1.072 seconds
Maximum number of seconds to run all queries: 1.569 seconds
Number of clients running queries: 20
Average number of queries per client: 0
now.. before you get all pissy at me, these installs are both from mysql.com, are BETA release using ‘default’ setups.. I know they need tuning.
so I decided to run the mysqlslap against blastwave’s mysql5 (5.0.19) which has a bit better default setup (IMHO)
sunfire $ mysqlslap -c 20 -i 20
Benchmark
Average number of seconds to run all queries: 1.647 seconds
Minimum number of seconds to run all queries: 0.882 seconds
Maximum number of seconds to run all queries: 2.783 seconds
Number of clients running queries: 20
Average number of queries per client: 0
still the same kind of numbers.
one thing I did find interesting was that I only saw one connection in the SHOW PROCESS LIST command.
any mysql guru’s want to tell me what I’m doing wrong on the test here?
update: this is what I get on a x86-64 machine.
$ bin/mysqlslap -c 20 -i 20 -a
Benchmark
Average number of seconds to run all queries: 0.002 seconds
Minimum number of seconds to run all queries: 0.002 seconds
Maximum number of seconds to run all queries: 0.003 seconds
Number of clients running queries: 20
Average number of queries per client: 0
same deal.. no tweaking of configurations, just download the tarball from mysql.com and fire it up.
anyone have any ideas?
SunFire progress -- the cable arrived
Posted by Ian Holsman
yes.. no more excuses.. time to open the box now.
If you want more photos see Ask’s
my Daughter Ainsley, will be in charge of the camera while I open and move the machine around.. it should make for a interesting photostream. you might even catch glimpse of my other family members as well.
right now my youngest is performing the ‘how many times can I jump on the machine before daddy freaks out’ benchmark..
The case of the missing servers
Posted by Ian Holsman
Compare the initial annoucnement and the recently announced rules just posted.
The Niagara team will make the decisions, and it’s in their sole discretion, but we’ve yet to place a limit on the number of systems we’ll give away
vs.
The judging panel will choose up to one (1) winner per Entry Period based on the highest scoring submission.
I guess they figured out what the limit will be. 1 per month. so I’m waiting until next month now..
Colm’s benchmark is too good to bother even opening up the box for (and I think he deserves it as well)
Older posts: 1 2