I have an update operation where I am able to update 10 million records in
approx
2.5 mins.
But when I tried to do the same update on say 40-50 million records, mysql
takes forever to finish. Its the same table, and same update operation, i am
just changing the range of ids using where claus
>Also, when a query takes too long I kill it by shutting down the
server, is this safe or is there a better alternative (MyISAM tables)?
Use show processlist to see the query that taking more time and use "
kill ; " for terminating the query .
--
Praj
Surendra Singhi wrote:
Hello Chris,
C
Hello Chris,
Chris <[EMAIL PROTECTED]> writes:
> Surendra Singhi wrote:
>> I am using mySQL 5.0 and I have 2 tables with few hundred millions of
>> records. To optimize things, I am using MyISAM tables, using the
>> smallest possible data
>> type and have set indexes.
>> Now, the problem which
Surendra Singhi wrote:
Hi,
I am using mySQL 5.0 and I have 2 tables with few hundred millions of
records.
To optimize things, I am using MyISAM tables, using the smallest possible data
type and have set indexes.
Now, the problem which I am facing is that mySql process is wasting lot of
time
Thanks, I changed the permissions, restarted, and everything is working
great now. Thanks a lot.
> Shaun wrote:
> > Thanks for your help Dathan, I will make the required changes. I just
have
> > one other problem.
> >
> > I'm not sure what queries don't use an index. I've attmepted to turn on
Shaun wrote:
Thanks for your help Dathan, I will make the required changes. I just have
one other problem.
I'm not sure what queries don't use an index. I've attmepted to turn on the
slow-queries-log, but nothing ever shows up in the file. Here's what I have
in the my.cnf
[mysqld]
skip-locking
se
Thanks for your help Dathan, I will make the required changes. I just have
one other problem.
I'm not sure what queries don't use an index. I've attmepted to turn on the
slow-queries-log, but nothing ever shows up in the file. Here's what I have
in the my.cnf
[mysqld]
skip-locking
set-variable
Shaun wrote:
Hello,
I was wondering if a more knowledgeable person could help me out with my
configuration and let me know how I could further optimize MySQL. Here's the
hardware on my dedicated server:
Processor #1 Vendor: GenuineIntel
Processor #1 Name: Intel(R) Pentium(R) 4 CPU 2.40GHz
Process
Look at
> Created_tmp_disk_tables 14768
> Created_tmp_tables 269520
> Created_tmp_files 3
Increase tmp_table_size = 64M:
it's used to stop going to disk and some internal mysql operations.
> Handler_read_rnd_next 58229817
Your tables are not
Joseph,
How big your table files are? Are they MyISAM or Innodb ? Do you have
indexes? How much memory do you have? Is your MySQL running on a
dedicated server or do you run anything else on your db server?
This questions needs to be answered before suggesting anything logical.
But general sugges
On Tue, Jan 22, 2002 at 10:12:55AM -0600, Solsberry, Glendon wrote:
> I have mySQL v3.23 running on a Mandrake 8.1 box (AMD 1600XP, 512MB
> RAM). The problem is that the main query (listed below) takes
> approximately 3 hours to run.
[snip]
Wow! Thanks for all the detail.
> The query is this
You need to set the max_connections variable like this in the my.cnf
file:
set-variable = max_connections=250
-- Jason
On Thu, 2001-12-27 at 11:38, Kim Albee wrote:
> We are trying to optimize mySQL. Right now, the max_connections is set to
> 100. We are only able to open 99 concurrent co
On Thu, Dec 27, 2001 at 10:38:42AM -0600, Kim Albee wrote:
> We are trying to optimize mySQL. Right now, the max_connections is set to
> 100. We are only able to open 99 concurrent connections to the db, and even
> then, some requests are unable to get a connection. We'd like to be able to
> sc
> I have used optimize table on several tables however it has not
> affected the
> speed of the queries or the large amount of processor resources that are
> being used.
>
> Have you heard of a way to rebuild a table more efficiently?
Go back and do this:
myisamchk -o *MYI
myisamchk -a *MYI
myisa
I'm not an expert, but I've never heard of a db getting slower after an
index rebuild. It's possible that's just a red herring.
You've been speaking generally about things being slower, I'd suggest you
get specific. Track down the queries are slow now, use EXPLAIN on them to
see what indexes
]]
Sent: Tuesday, June 26, 2001 11:33 AM
To: Mysql
Cc: "Michael Blood"
Subject: Re: Optimizing MySQL
> Recently the index files became corrupted and I ran the
> myisamchk *.MYI -r -S to repair them.
Try an OPTIMIZE TABLE or ANALYZE TABLE. Your queries may be using the
incorrect i
> Recently the index files became corrupted and I ran the
> myisamchk *.MYI -r -S to repair them.
Try an OPTIMIZE TABLE or ANALYZE TABLE. Your queries may be using the
incorrect indexes since the statistics have not been updated.
You can also do this: myisamchk *.MYI -a
Sincerely,
Steven Rouss
17 matches
Mail list logo
