List:General Discussion« Previous MessageNext Message »
From:Marc Slemko Date:July 5 2004 4:58pm
Subject:Re: Concurrency Question
View as plain text  
On Mon, 5 Jul 2004 16:07:58 +0100 , Javier Diaz <jdiaz@stripped> wrote:
> We have changed all our tables to InnoDB and now the server is not able to
> handle the load, even when we are not running the SELECTs statements against
> these tables yet.
> As I mentioned in my email we make a lots of INSERTS and UPDATES in these
> tables (more than 3000 per second). So far using MyISAM everything was OK,
> but now when we moved the tables to InnoDB (to be able to make Read/Write
> operations in these tables) the performance was down completely and the
> server can not handle it.
> Does anyone have a rough idea when you change from MyISAM to InnoDB how the
> performance is affected?

That all depends on how you are using transactions.  If you are trying
to do each of these operations in a separate transaction, then
definitely that will be a problem since transactions inherently have a
certain cost to them since they need to commit changes to durable

If this is the case, then a horribly ugly "now you don't have
durability any more in your transactions" hack you could try is
setting innodb_flush_log_at_trx_commit to 2, see the docs for details.
 Be warned that doing so means you can loose committed transactions if
the machine crashes.
Concurrency QuestionJavier Diaz2 Jul
  • Re: Concurrency QuestionAlec.Cawley2 Jul
  • Re: Concurrency QuestionEgor Egorov6 Jul
RE: Concurrency QuestionJavier Diaz5 Jul
  • Re: Concurrency QuestionMarc Slemko5 Jul
  • Re: Concurrency QuestionJosh Chamas5 Jul
RE: Concurrency QuestionJavier Diaz5 Jul
  • Re: Concurrency QuestionMarc Slemko5 Jul
RE: Concurrency QuestionPaul DuBois5 Jul
RE: Concurrency QuestionMarvin Wright12 Jul
  • RE: Concurrency QuestionJoshua Chamas12 Jul
Re: Concurrency QuestionHeikki Tuuri13 Jul