Way ahead of you, that switch was turned on during initial load before we went live with the new servers.

Mark Leith wrote:

You mention that MySQL is "only using 1.5 gig"..

Out of interest, are you aware that Windows by default when using
"large" amounts of memory, will split the memory allocation down the
middle - between "applications" and "system"? So given your 4Gb of
memory, applications with be getting 2Gb..


You can read more about this here:

http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx

Basically, add a \3GB switch to your boot.ini file.

Then you can start look at tuning the memory on MySQL as well..

HTH

Mark

Mark Leith Cool-Tools UK Limited
http://www.cool-tools.co.uk



-----Original Message-----
From: matt_lists [mailto:[EMAIL PROTECTED] Sent: 28 April 2005 13:57
To: Gleb Paharenko
Cc: mysql@lists.mysql.com
Subject: Re: Maximize mysql ini for 4gig big query win 2003 box



I'm more concerned with mysql only using 1.5 gig, wouldnt it be faster to maximize memory usage? The only thing these box's do is mysql



I do have slow queries, but they are big joins across all the big tables, and users doing querys on tables without using a key, the contract requires dynamic query on any fields, and the tables are too big to index every possible key combination they would use (30-40 columns on some)


So far, I've got no major issues, aside from big queries and there's no way around that, unless mysql changes on how it combines indexes, ie it does not combine them currently.

Matt


Gleb Paharenko wrote:



Hello.

SHOW STATUS and a piece of SHOW PROCESSLIST
with slow queries could give additional information,
so the probability of the helpful answer grows.

matt_lists <[EMAIL PROTECTED]> wrote:




Anybody have any suggested settings for our my.ini ?

4 gig box, running windows 2003

peak memory usage for mysql is 1.4 gig currently

using myisam files, lots of little index querys, and some very large
queries at night

615 tables, 88.3 gb of myd,  45.2 gb of myi, 33 of the tables/indexes
break 1 gig, largest is 6 gig

if you discount the piddly little tables, there are only 125 tables with
size that matter, ie larger than 50mb



Here's what we have now, sugestions welcome

max_connections=100
query_cache_size=512M
query_cache_type=1
table_cache=1024
tmp_table_size=400M
thread_cache_size=8
myisam_max_sort_file_size=100G myisam_max_extra_sort_file_size=100G
myisam_sort_buffer_size=369M
key_buffer_size=318M
read_buffer_size=64K
read_rnd_buffer_size=256K
sort_buffer_size=256K
open-files-limit=500
myisam-recover=BACKUP,FORCE
memlock



















-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to