Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

mysql and volume



On Thu, 15 May 2003 17:18:52 -0400
FRamsay at castelhq.com wrote:

> 
> Ok, how well does mysql handle very high volume... say 200,000+
> transactions per hour.
> The configuration would be very simple, one server one db, no backup
> server(fault recovery would be a reset of the DB).
> And the transactions would mostly be updates and selects.
I suggest that you visit the MySQL site (and possibly look at their
professional product). Secondly, you might visit http://sitepoint.com.
The guy who runs that site, Kevin Yank, is an author who also uses MySQL
very heavily. I bought his book after downloading the first 4 chapters. 

I don't have any figures on MySQL performance per se. I can tell you
that Berkeley DB definitely would not stand up to that type of stress. 

When at Polaroid on contract, I implemented a database based on Al
Stephen's public domain btree based system. We used it for drivers
license demographics in another state. I believe that Ingress had been
used in another state. When they hit a bug in Ingress, they could not
get a fix (at least in a reasonable time frame). So, your considerations
should also be things like backup/restore, and time to repair a bug.
Relational databases like MySQL may not have the performance that a
non-relational engine might, but the other consideration is the nature
of the queries (eg selects). 

The other consideration is the hardware. With that kind of volume, you
are going to stress the hardware. I am assuming that you have an Intel
based PC server and not a commercial Unix machine, such as Sun, IBM, HP
or HP/Compaq.  

-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20030516/84e6c312/attachment.sig>



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org