List:General Discussion« Previous MessageNext Message »
From:Jake Maul Date:November 11 2008 10:18pm
Subject:Re: Tuning a MySQL desktop database
View as plain text  
I have only 3 things worth mentioning:

You might want to lower max_connections... wouldn't want someone to
actually start *using* 100 connections on a desktop box that only has
256MB RAM to begin with... it'll be in swap instantly (if it isn't
already, before you've even started MySQL).

Why InnoDB? If you're looking at low-concurrency (5 user max, you
said) and low memory usage, you might want to leave it at the default
of MyISAM, and then use 'skip-innodb' for the memory savings... unless
you've got a good reason to change it. It's not a lot, but with only
that small amount to work with every little bit will help. That'll
save you $innodb_buffer_pool_size amount of memory at least (plus the
actual InnoDB code itself).

Depending on what you're trying to do, you might want to consider
something like SQLite or HSQLDB instead. Both should be more
lightweight than MySQL.

As for other tweaks to make to MySQL itself, I don't have much to
offer. Most tweaks depend almost entirely on the workload in
question... like another respondent said, if there were tweaks that
everyone used, they'd be the defaults by now :).

You might try out these two scripts... they've been very helpful
diagnosing MySQL performance issues for me on Linux servers. Good luck
getting them going on Windows though... Cygwin might be necessary :)


2008/11/11 RP Khare <passionate_programmer@stripped>:
> Thanks for the answer.
> Maximum five users will work. The machine on which I am testing is the
> minimum configuration my client has. Attached is the "My.ini" file.
> .........
> Rohit.
>> Date: Tue, 11 Nov 2008 16:21:07 +0100
>> From: Joerg.Bruehe@stripped
>> Subject: Re: Tuning a MySQL desktop database
>> To: passionate_programmer@stripped
>> CC: mysql@stripped
>> Rohit,
>> RP Khare wrote:
>> > We are testing MySQL in production environment with real data. When the
>> > application is ready and all tests have been conducted well, we will
> finally
>> > migrate to MySQL Enterprise.
>> >
>> > At present our application is running on a desktop machine with MySQL
>> > 5.1 Community Edition installed on it. MySQL 5.1 is using default settings.
>> >
>> > Machine is: Pentium 4 with 256 MB RAM.
>> >
>> > What settings I need to change to tune MySQL?
>> I really do not want to offend you, but the question is silly.
>> If there were some way to definitely improve MySQL's performance without
>> causing any drawbacks or problems, it would be used in the default
>> settings.
>> Default settings are meant to be usable for many installations, but
>> cannot be optimum for all. Users can leave them as provided and start
>> running their application, watch them, and check whether there are some
>> bottlenecks.
>> Once they see these, they can change the settings so as to avoid or at
>> least reduce these bottlenecks (as much as the hardware permits).
>> We readers here will never know what your bottlenecks are unless you
>> tell us. It might be cache sizes, number of concurrent users, select
>> strategies, ...
>> The only general remark I dare make: 256 MB may be very little RAM for
>> most database servers, will be sufficient only if you have few users,
>> not much data, or can tolerate slow response times.
>> Jörg
>> --
>> Joerg Bruehe, MySQL Build Team, Joerg.Bruehe@stripped
>> Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
>> Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
>> Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB161028
> ________________________________
> What's on the ramp today could be on the streets tomorrow. Keep up with
> trends on MSN Lifestyle Try it!
> --
> MySQL General Mailing List
> For list archives:
> To unsubscribe:
Tuning a MySQL desktop databaseRP Khare9 Nov
  • Re: Tuning a MySQL desktop databaseSalah Nait-Mouloud9 Nov
    • RE: Tuning a MySQL desktop databaseMartin Gainty9 Nov
  • Re: Tuning a MySQL desktop databaseJoerg Bruehe11 Nov
    • RE: Tuning a MySQL desktop databaseRP Khare11 Nov
      • Re: Tuning a MySQL desktop databaseJake Maul11 Nov
RE: Tuning a MySQL desktop databasemos12 Nov