(to answer a couple of posts at once):
Our machine was seeing less than 20 connects / sec. The problems
continued after we broke largeish (although only about 350,000 records,
indexed) tables into smaller ones and verified/optimized all code that
makes mysql queries. We have a good mix of selec
I have posted before regarding a problem with mysql 3.23.41 hitting some
sort of threshold limit and spawing threads like crazy. I have seen
others post here with the exact symptoms, from what I understand these
are all linux boxen. I have personally tested it with the 2.4 series of
kernels, and
PHP's mysql_fetch_array() fetches an associative as well as indexed array...or you
can specify which. (I'm a huge fan of perl, btw, and have used it to talk to
mysql when PHP was just a baby language so no flames...just setting the record
straight...)
Cheers
jenn
Rich Duzenbury wrote:
> > PH
Today our servers got the highest consistant level of activity I've ever
seen, almost all of it because our users were reloading a mysql-database
driven message board like crazy.
Fortunately, I was awakened at 7.30am by my mysql 3.23.41 machine dying
again, and in utter frustration I backed off
Has anyone tried dropping back several versions to see if this still happens? I
tried running 3.23.38, and still had problems, but will be dropping back to
possibly even 3.22 to see what happens. I know that linux kernel 2.4 handles
memory sometimes in a strange way, but this problem that I am s
I'm running mysql 3.23.41 on a PIII 800 Mhz machine with 512MB RAM,
linux kernel 2.4.7, dedicated machine (ie, not running anything other
than MySQL). I've been running mysql in a production environment for
nearly 2 years, moderately hit (500,000 - 800,000 database connects per
day) with no probl
