Made these changes, per my-huge.cnf. Thanks for the tip, Lars! We should probably "officially recommend" that people use my-huge.cnf and uncomment its InnoDB settings for big databases on big hardware.
skip-locking key_buffer = 384M # my-huge.cnf max_allowed_packet = 4M # larger packets table_cache = 512 # my-huge.cnf sort_buffer_size = 2M # my-huge.cnf read_buffer_size = 2M # my-huge.cnf read_rnd_buffer_size = 8M # my-huge.cnf myisam_sort_buffer_size = 8M # my-huge.cnf thread_cache_size = 8 # my-huge.cnf query_cache_size = 64M # more cache. thread_concurrency = 4 # CPU's * 2 Aaron On Wed, 2006-10-25 at 10:29 +0200, Herr Lars Kneschke wrote: > Aaron Stone <[EMAIL PROTECTED]> schrieb: > >And as for InnoDB, I cranked everything up like crazy, and basically get > >most of my database in memory. If you have 4GB of RAM, I think it's > >entirely reasonable to put a gig into MySQL buffering. But, again, no > >hard numbers to back these up :-\ > > As one MySQL instance is only 1 process with multiple threads, you are > limited to 2 GByte per process on 32bit systems. Only 64bit systems can use > more than 2 GByte per process.Just a reminder of the total amount a single > process can use on 32bit systems. To much query cache can slow down the > system.You can simply have a look at the examples delivered with MySQL > itself. There is a file called my-huge.cnf. On Ubuntu you can find this file > in /usr/share/doc/mysql-server-5.0/examples/ > -- > Lars Kneschke > Metaways Infosystems GmbH > Pickhuben 4 > 20457 Hamburg > Germany > > eGroupWare Training & Support ==> http://www.egroupware-support.net > > E-Mail: mailto:[EMAIL PROTECTED] > Web: http://www.metaways.de > Tel: +49 (0)40 317031-21 > Fax: +49 (0)40 317031-81 > Mobile: +49 (0)175 9304324 > > > > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
