On 1/13/11 3:51 PM, Reindl Harald wrote:
Are you sure that the lags are really the query and not the connection?
I have seen on a windows server with ipv7 large lags because mysql
treid by every connect to make a dns-reverse-lookup first on ipv6
and after fail ipv4
"skip-name-resolve" in the my
Am 13.01.2011 22:13, schrieb Steve Staples:
> the only writes that happen, is when a customer has their "status"
> changed, password updates, or they change their name, OR when a new
> customer is created. I would say a new customer get created (insert
> into) about 30 times per day, and a cus
On 1/13/11 2:13 PM, Steve Staples wrote:
On Thu, 2011-01-13 at 13:51 -0700, Steve Meyers wrote:
On 1/13/11 1:21 PM, Steve Staples wrote:
table type is MyISAM, it is a "customer_account" table, which holds the
email address, and the customer_id field, the queries that are
constantly being quer
On Thu, 2011-01-13 at 13:51 -0700, Steve Meyers wrote:
> On 1/13/11 1:21 PM, Steve Staples wrote:
> > table type is MyISAM, it is a "customer_account" table, which holds the
> > email address, and the customer_id field, the queries that are
> > constantly being queried is "select customer_id from
On 1/13/11 1:21 PM, Steve Staples wrote:
table type is MyISAM, it is a "customer_account" table, which holds the
email address, and the customer_id field, the queries that are
constantly being queried is "select customer_id from customer_account
where customer_email = '' and `status`='1';
Do
On Thu, 2011-01-13 at 15:07 -0500, Michael Dykman wrote:
> The behaviour of mixed reads/write o your system is heavily dependant
> on what types of tables you are using. The fully ACID tables types,
> most notably InnoDB support that model far better than MyISAM tables..
> Not to discount the val
The behaviour of mixed reads/write o your system is heavily dependant
on what types of tables you are using. The fully ACID tables types,
most notably InnoDB support that model far better than MyISAM tables..
Not to discount the value of measuring your raw i/o performance, but
first we should det
On 1/13/2011 1:44 PM, Steve Staples wrote:
Hello,
I've been noticing a little lag in my application lately, it seems as
if 1 table in 1 database is getting slower to read from. Mind you,
that table is being accessed a LOT of times per second every hour of
every day, and then the "application"
(Assuming you are on Linux)
Take a look at the output of: iostate -xk 60
The output will update every 60 secs. Take a look at the value in the %util
column after a few updates, if it's around 90% you have become disk bound
and you'll need to figure out a way to decrease some load on the disk. You
Hello,
I've been noticing a little lag in my application lately, it seems as
if 1 table in 1 database is getting slower to read from. Mind you,
that table is being accessed a LOT of times per second every hour of
every day, and then the "application" searches on this same table too.
In my sand
10 matches
Mail list logo
