From: Jeremy Kemper <jeremy@...>
Date: 2007-03-07T13:19:15+09:00
Subject: Re: High ActiveRecord CPU Utilization

------=_Part_181846_13183719.1173241152076
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 3/6/07, Brian Adkins <lojicdotcomNOSPAM@gmail.com> wrote:
>
> When running a test that primarily involves loading up a few MySQL
> tables with ActiveRecord objects, I was surprised to see the Ruby CPU
> utilization at 93% and the MySQL CPU utilization at 7%. I would expect
> this workload to be heavier on MySQL than that.
>
> I would think inserts (particularly with updating several foreign key
> indices) would tax the database more than Ruby.
>
> Has this been other folks' experience? Is running in the test
> environment incredibly different than production with respect to CPU
> utilization? I suppose my next step is to run in production to see what
> kind of results I get.


Hey Brian, could you start this conversation on the Rails list? It's a
pretty narrow topic.

(In short: yes. Record instantiation and save are slow relative to the
database. In the big picture, page rendering is typically slower still.)

jeremy

------=_Part_181846_13183719.1173241152076--