-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 19 November 2002 23:34, Steven Roussey wrote:
> OK, it seems to be working. The load is not spiraling out of control. :)
Thanks! This is very reassuring. I will start building 4.0.5a Linux binaries
right away.
Bye,
LenZ
- --
For
OK, it seems to be working. The load is not spiraling out of control. :)
Sincerely,
Steven Roussey
http://Network54.com/
> -Original Message-
> From: Lenz Grimmer [mailto:[EMAIL PROTECTED]]
> Before I make a 4.0.5a release of the Linux binaries (and finally
announce
> 4.0.5), could som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 19 November 2002 12:19, Lenz Grimmer wrote:
> On Monday 18 November 2002 19:52, Steven Roussey wrote:
> > :( Sadly, 4.0.5 does _not_ fix this issue. I just tried it and our load
> >
> > went from 1 to 145 in 20 seconds...
>
> Thanks for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 18 November 2002 19:52, Steven Roussey wrote:
> :( Sadly, 4.0.5 does _not_ fix this issue. I just tried it and our load
> went from 1 to 145 in 20 seconds...
Thanks for the info! I don't get it. We will investigate, why this problem has
su
> > With 3.23.53a everything works fine.
>
> MySQL 4.0.4 was compiled against a wrongly built glibc, which leads to
the
> above mentioned behaviour. Please download MySQL 4.0.5, which has just
been
> released and should fix this problem:
:( Sadly, 4.0.5 does _not_ fix this issue. I just tried it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 18 November 2002 14:53, Stefan Bohm wrote:
> since I've upgraded to 4.0.4 I'm experiencing serious problems.
> When mysql starts up, everything is fine (~50 req/sec, ~10 threads)
> and the system load is about 1.0.
>
> After a while, the num
