Thanks James. I'll definately give that a try. My test server has 1 gig of ram. In the
my-huge.cnf example it says that it's mainly for servers that have mysql as the main
process. On my production server, I have 1 gig of ram, but it also runs apache, mutliple
webstites, mysql, DNS, ftp server, etc... It's a dedicated server that only hosts my
sites so I can tweak the configuration. Should I use the my-large.cnf as a starting
point, or should I be OK with my-huge.cnf?
James Harvard <james.lists.tech@stripped> wrote:The reason I suggested
that you just use the alternative my-huge.cnf file is because that is a ready-prepared
config file optimised for systems with lots of RAM for MySQL to use. You don't need to
know which variable to change - it's already done for you. You may want/need to tweak
stuff later, of course, but my-huge.cnf is a better starting point than my.cnf.
At 6:45 am -0800 23/12/05, Grant Giddens wrote:
>I think that the reason the original query is so slow is that I don't have enough
> RAM allocated to mysql. When the original query takes place, I see a process "Copying to
> tmp table on disk". I believe it's writing all the data to the disk and then sorting it.
> I'd like to try tweaking the my.cnf file to allow mysql to use more RAM. I just need
> someone to help me edit the file because I'm not quite sure what I'm doing...
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=1
Find Great Deals on Holiday Gifts at Yahoo! Shopping