Hello.
On Thu 2002-10-31 at 08:10:17 -0600, [EMAIL PROTECTED] wrote:
> We are experiencing some issues with performance on a non-MySQL box and are
> looking for alternatives (and alternative methods). Once of the issues that
> we seem to be facing, is that the pure volume of data which needs to be
> pushed out. The other database is pushing out (at peak) 12.5 megabytes per
> second and is being hit with 30-45 queries per second. If we rework the
> application, we end up with one of two solutions:
Hm. Have you excluded that you simply hit a hardware bottleneck?
12.5MB sounds a lot like the limit of a 100MBit line.
> 1) move to MySQL for the database engine (it currently is MSSQL)
> 2) Rework the application, so that the application still talked to MSSQL,
> but we generate static pages (this is for a website) and store them in
> MySQL, which are then served. This will reduce both bandwidth and queries
> per second. Bandwidth is unknown, but the queries per second are estimated
> at 15-25 queries per second. The select statements would be very generic
> though (select * from table where ID='abc123')
>
> This leaves one major question. How much data can MySQL push out?
>
> Can MySQL handle 12.5 megabytes (not megabits) per second of data?
> Will MySQL handle 20 queries per second?
20 queries of the simple form
(select * from table where ID='abc123')
are no problem for MySQL. It is able to sustain several thousand of
such queries per second on a common desktop PC (given that the
relevant data fits into memory).
If you had so much data that disk access is _always_ necessary
(i.e. >100GB), and therefore disk access is the absolute bottleneck,
you can expect about 50/sec -100/sec, because that directly correlates
to the disk seek time. You can get more with RAID. But remember, that
this is the absolute worst case.
The real performance you will experience will be somewhere in
between. The limiting factor with MySQL in your case should not to be
the number of queries, but the size (i.e. throughput).
> I know a lot of this also determined by OS/hardware. MySQL would be
> running on a 2-CPU Sun box.
Sorry, I do not have much experience with MySQL on Suns (at least not
in pushing it to the limits). On an Athlon 700Mhz selecting 10000
random rows out of 60000, I get over 330MB/sec (1000 queries/sec) on
localhost and about 5.5MB/sec via a 100MBit TCP connection using the
mysql command line client like this:
cat test.sql | mysql --raw testdb > /dev/null
HTH,
Benjamin.
--
[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
