sheeri kritzer schrieb:
No problem:
Firstly, how are you measuring your updates on a single table? I took
a few binary logs, grepped out for things that changed the table,
counting the lines (using wc) and then dividing by the # of seconds
the binary logs covered. The average for one table was 108 updates
per second.
I'm very intrigued as to how you came up with 2-300 updates per second
for one table. . . did you do it that way? If not, how did you do it?
(We are a VERY heavily trafficked site, having 18,000 people online
and active, and that accounts for the 108 updates per second. So if
you have more traffic than that. . .wow!)
Thanks for your hardware/database information. I will look at that close
tomorrow since I want to go home for today - it's already 9 pm over
here... I need beer ;)
We are not running a webservice here (actually we do, too, but thats on
other systems). This is part of our database with data of major stock
exchanges worldwide that we deliver realtime data for.
Currently that are around 900,000 quotes, during trading hours they
change all the time... We have much more updates than selects on the
main database.
Our Application that receives the datastream writes blocks (INSERT ...
ON DUPLICATE KEY UPDATE...) with all records that changed since the last
write. It gives me debug output like "[timestamp] Wrote 19427 rows in 6
queries" every 30 seconds - and that are numbers that I can rely on.
Jan
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
