On Sun, Mar 11, 2001 at 01:16:20AM -0500, Justin wrote:
>
> Well thats good to know.. although this is sustained 24x7x365
My average rate over the last 67 days is about 52/second. In reality
we have some periods of much higher load (several hundred per second)
and some of much lower load. It is just about to hit the 300,000,000
query mark since it was last shut down (for the upgrade 67 days ago).
I'd like to hit a billion queries before the next downtime, but who
knows...
I'm currently running 3.23.29-gamma using the staticly linked version
from mysql.com.
> in an attempt to get stability, I've been running on the official
> 3.22.32 mysql binary for a month now .. it hasn't helped.
I'd highly recommend upgrading to 3.23.xx. You should see better
performance with MyISAM tables. I'd also highly recommend using a
static binary from the mysql web site.
> Typically indexes get corrupted and cause selects to malfunction,
> OR, cause mysqld to crash, OR cause count(*) or distinct(*) queries
> to run in infinite loops, but not necessarily on the corrupt table.
> it seems to me index corruption can poison the server beyond the
> afflicted table.
Certainly can. If a thread starts to suck cpu time, the whole system
will suffer and start to spiral down into places you'd rather not
look.
Jeremy
--
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 328-7878 Fax: (408) 530-5454
Cell: (408) 439-9951
---------------------------------------------------------------------
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
