cache, so can can do
some things without taking MySQL down.
- Original Message -
From: "Ratheesh K J" <[EMAIL PROTECTED]>
To:
Sent: Thursday, July 27, 2006 8:38 AM
Subject: MySQL performing too badly under heavy load - urgent hlp needed
Hello all,
Stuck up with a
t; e) any combination of the above
f) not enough memory, that forces major swapping activity
-Stathis
>
> Ratheesh K J wrote:
> > Hello all,
> >
> > Stuck up with a major problem. Urgent hlp required
> >
> > MySQL seems to be performing too bad during heavy load o
At 09:38 AM 7/27/2006, Ratheesh K J wrote:
Hello all,
Stuck up with a major problem. Urgent hlp required
MySQL seems to be performing too bad during heavy load on the server.
Queries which normally take around 5 secs to complete are taking more than
1000 secs to complete during load.
What
QL seems to be performing too bad during heavy load on the server. Queries
which normally take around 5 secs to complete are taking more than 1000 secs to
complete during load.
What could be the reason. Show processlist shows many process in sending data
state. All tables are of INNODB type. B
Hello all,
Stuck up with a major problem. Urgent hlp required
MySQL seems to be performing too bad during heavy load on the server. Queries
which normally take around 5 secs to complete are taking more than 1000 secs to
complete during load.
What could be the reason. Show processlist shows
On Monday 04 October 2004 01:18 am, Batara Kesuma wrote:
> I have a cron running this every night.
> DELETE message_inbox FROM message_inbox LEFT JOIN message ON message.id
> = message_inbox.message_id WHERE message.id IS NULL
>
> Message table also has about the same amount of rows.
>
> I notice t
Hi,
I just noticed that replication on my servers failed when they were
under heavy load. I have 1 master and 2 slaves.
For example, I have table for all incoming messages.
message_inbox | CREATE TABLE `message_inbox` (
`member_id` mediumint(8) unsigned NOT NULL default '0',
`
t; Sent: Wednesday, August 20, 2003 3:57 PM
> To: [EMAIL PROTECTED]
> Subject: MySQL 4.0.13 Memory problem under heavy load
>
>
> Hi all,
>
> I want to get your opinions on how to increase available/free
> memory and performance on a heavy volume database server.
>
>
space)
started to suffer from memory outages because of heavy load. During day
available free memory is changing from 200Mb to 5Mb and when available memory
reaches to 5Mb MySQL starts to give 'Too many connections' messages. Db server
is working with 45-70 query/second and more than 25,712
ecently our master database server (2 AMD Cpu + 2Gb memory + 2Gb swap
> space) started to suffer from memory outages because of heavy load.
> During day available free memory is changing from 200Mb to 5Mb and when
> available memory reaches to 5Mb MySQL starts to give 'Too many
>
t: MySQL 4.0.13 Memory problem under heavy load
> Hi all,
>
> I want to get your opinions on how to increase available/free memory and
> performance on a heavy volume database server.
>
> I have MySQL 4.0.13 running on RH 7.2 replicated to another RH 7.2 using
> same MySQL versio
space) started to suffer from memory outages because of heavy load.
During day available free memory is changing from 200Mb to 5Mb and when
available memory reaches to 5Mb MySQL starts to give 'Too many
connections' messages. Db server is working with 45-70 query/second and
more than 25,712
<[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 6:45 PM
Subject: Re: MySQL Server Crashes under heavy load
> We have a site with a similar architecture:
> - 6 load balanced front-ends
> - 1 dedicated database server (Dual P3 1.4GHz, 2GbRAM, RH7.2)
> we serve around 3 mill
We have a site with a similar architecture:
- 6 load balanced front-ends
- 1 dedicated database server (Dual P3 1.4GHz, 2GbRAM, RH7.2)
we serve around 3 million pages/day (all pages are dynamiquely generated,
each page needs an average of 15 SQL queries).
What we have done:
- audit ALL SQL queries
We are hosting a high volume site that gets about 1 million page views a day
on RedHat 7.3. We currently have 3 load balanced servers on the front end
accessing a MySQL server on the back end. The MySQL servers is dual P3 1ghz
with 1 GB of RAM and when the MySQL queries hit about 50 per second, t
Hi
we have what we think is a bug regarding an insert (or an update) during times of
heavy load on the mysql server. Our application should perform an insert in one table
and updates on two other tables but the insert is performed up to 9 times.
I'm not entierly sure that the problem is N
Hi,
I am using MySQL 3.23.41 and JDBC to support some servers. When I stress the servers I
get several errors like
java.sql.SQLException: General error: Table testtab was not locked with LOCK TABLES
I get this error on some of the insert attempts, and on half of the update attempts.
I also tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
any ideas what could be causing this?
this happens when apache has reached its max_client limit.
using 3.23.45
011127 18:16:30 InnoDB: Started
/home/attila/mysql-max-3.23.45-pc-linux-gnu-i686/bin/mysqld: ready for
connecti
011127 18:35:45 re
At 06:34 PM 5/26/2001 +0200, P.Agenbag wrote:
>How will I know if my server is up to it, or should I rather say, how
>many consecutive users will this box be able to handle? The line
>shouldn't be a problem, I think it sits on a couple of 100 MB/s line.
>
Well.. this is one topic I sorta specia
drives on a different SCSI
controller)
- Original Message -
From: "P.Agenbag" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, May 26, 2001 9:34 AM
Subject: heavy load configuration
> I have a Linux box running mysql and apache, and we are expecting qui
I have a Linux box running mysql and apache, and we are expecting quite
a load on the 1st of June. We have an application form whose data will
be written into a db on the same server and I would like to know what I
can do to make sure things go smooth.
The machine is an AMD 500, with 320MB RAM, 25
On Mon, Mar 19, 2001 at 04:06:29PM +0300, Anatoly Chubais wrote:
> Hello!
>
> There's a need to design a system (something like online forum) that
> will be storing huge amount of small messages in database. There
> must be fast access only to messages for the last 3 days (guess this
> means tha
Hello!
There's a need to design a system (something like online forum) that will be
storing huge amount of small messages in database.
There must be fast access only to messages for the last 3 days (guess this means
that main table with indexes on it must be kept small?), while other messages
ca
Hello everybody!
I've just switched from version 3.23.29a-gamma to 3.23.35 and noticed
a very high system load increase. As I switched back, everything worked
fine again.
Can anyone agree with this?
As I'm using the replication feature I like to use always
a recent version. This host is a maste
er of queries
sent to the database increases, or the CPU usage
increases under heavy load, mysql crashes. This has
been a consistent behaviour. The system is under
testing phase and the servers just give up under a
reasonably heavy load.
This is the my.cnf file -
[mysqld]
skip-locking
set-var
On Fri, Mar 16, 2001 at 12:17:41PM +0300, áÎÁÔÏÌÉÊ âÏÒÉÓÏ×ÉÞ wrote:
> Hello!
>
> There's a need to design a system (something like online forum) that will be
>storing huge amount of small messages in database.
> There must be fast access only to messages for the last 3 days (guess this means
>
Hello!
There's a need to design a system (something like online forum) that will be storing
huge amount of small messages in database.
There must be fast access only to messages for the last 3 days (guess this means that
main table with indexes on it must be kept small?), while other messages
Hello!
There's a need to design a system (something like online forum) that will be storing
huge amount of small messages in database.
There must be fast access only to messages for the last 3 days (guess this means that
main table with indexes on it must be kept small?), while other messages
28 matches
Mail list logo
