← Back to team overview

randgen team mailing list archive

Re: Make changes in Rev 662 (Jan 11) for restricted mysqld mem usage optional?


You are right, I went overboard with this and only produced limited benefit when it comes to preserving memory.

I will revert the original change shortly and push it again as you suggested, with --low-memory.

Philip Stoev

----- Original Message ----- From: "John H. Embretsen" <johnemb@xxxxxxxxx>
To: <randgen@xxxxxxxxxxxxxxxxxxx>
Sent: Thursday, January 13, 2011 2:36 PM
Subject: [Randgen] Make changes in Rev 662 (Jan 11) for restricted mysqld mem usage optional?

Philip (primarily),

Regarding your commit of January 11:

On 01/11/11 14:00, noreply@xxxxxxxxxxxxx wrote:
revno: 662
committer: eve<philips@eve>
branch nick: randgen-memory
timestamp: Tue 2011-01-11 14:57:27 +0200
restrict mysqld memory usage in an attempt to allow running more than one RQG test simultaneously without having to buy 16Gb of ram

Can you please make the changes to runall optional, e.g. by introducing an RQG option "--low-memory" or something like that?

The reasoning is that:

a) We would sometimes like to run with some of these settings as default in the server being tested (especially InnoDB, MyISAM), without setting them explicitly.

b) InnoDB in 5.0 and 5.1 fails to boot with loose-innodb-buffer-pool-size=4M:

From server log (5.0/5.1):

InnoDB: Doublewrite buffer not found: creating new
InnoDB: Cannot create doublewrite buffer: you must
InnoDB: increase your buffer pool size.
InnoDB: Cannot continue operation.

thank you,


Mailing list: https://launchpad.net/~randgen
Post to     : randgen@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~randgen
More help : https://help.launchpad.net/ListHelp