hey..
thanks for the info...
This is the my.cnf file that i'm using -
[mysqld]
skip-locking
set-variable= key_buffer=640M
set-variable= max_allowed_packet=10M
set-variable= table_cache=640
set-variable= sort_buffer=6M
set-variable= record_buffer=6M
set-variable=
We've had fairly bad luck with Linux 2.2.X and SMP for any kind of high-end
system. The DAC 960 SCSI controllers proved to be fairly problematic in this
environment. Sometimes updating the drivers helps. We have a couple of
systems that run much better when we do not use one of the
Justin writes:
Thank you Sinisa,
I actually did try the upgade, but rapidly reverted due to errors
such as these:
mysqld got signal 11;
stack range sanity check, ok, backtrace follows
0x812cfea
0x809f541
0x809da87
:
:
etc
AND...
read_const: Got error 127 when
On Saturday 10 March 2001 22:16, Justin wrote:
Well thats good to know.. although this is sustained 24x7x365
linux 2.2.14-5.0smp, uptime 170 days but e2fsk ok's the
the database partition, which is a mirror.
in an attempt to get stability, I've been running on the official
3.22.32 mysql
Justin writes:
What is your key buffer size? In my case, key buffer size is set
to 384mb .. and mysqld starts out small, perhaps 18mb and grows
within a day to 100mb, and within a few days to pretty much 300+mb
..so it is doing what one would expect it to.
The other mem parameters
Justin wrote:
What is your key buffer size?
mysql show variables;
ERROR 2006: MySQL server has gone away
No connection. Trying to reconnect...
Connection id:47881
Current database: *** NO ONE ***
|
| key_buffer_size |
Thank you Sinisa,
I actually did try the upgade, but rapidly reverted due to errors
such as these:
mysqld got signal 11;
stack range sanity check, ok, backtrace follows
0x812cfea
0x809f541
0x809da87
:
:
etc
AND...
read_const: Got error 127 when reading table ./
read_next_with_key: Got
Today I was having more index corruption problems.. the fact
that it typically happens on the *biggest* and *busiest* tables
leads me to believe that the request rate on my database
might be right off the scale compared to other users, who are
not reporting corruptions nearly as often.
My
On Sat, Mar 10, 2001 at 06:41:20PM -0500, Justin wrote:
Today I was having more index corruption problems.. the fact that it
typically happens on the *biggest* and *busiest* tables leads me to
believe that the request rate on my database might be right off the
scale compared to other users,
Well thats good to know.. although this is sustained 24x7x365
linux 2.2.14-5.0smp, uptime 170 days but e2fsk ok's the
the database partition, which is a mirror.
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.
Typically
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
I have a server that averages 256 queries/sec.
It maxes out at 1187 queries/sec.
It averages about 100 threads and maxes out at about 300.
I've never experienced the problems below with corrupted tables, but I
have been experiencing an interesting problem lately.
Normally the server uses about
What is your key buffer size? In my case, key buffer size is set
to 384mb .. and mysqld starts out small, perhaps 18mb and grows
within a day to 100mb, and within a few days to pretty much 300+mb
..so it is doing what one would expect it to.
The other mem parameters combine in ways explained in
13 matches
Mail list logo
