DB query time always 0 in production

rubyonrails-talk
1

Hello,

My DB time always shows 0.00000 in production, using thin, mongrel, rails 1.2.6, 2.0.2, it doesn't matter. In development, the DB time is correctly non-zero. I don't do any caching.

Is this a known problem?

Processing ProjectsController#index (for x.x.x.x at 2008-03-01 12:04:06) [GET]   Session ID: xxxx   Parameters: {"action"=>"index", "controller"=>"projects"} Rendering template within layouts/main Rendering projects/index Completed in 0.09227 (10 reqs/sec) | Rendering: 0.03694 (40%) | DB: 0.00000 (0%) | 200 OK [http://yyyy.yyy.yyy/\]

2

I copied development.rb to production.rb and still have the same problem. I suspect database timing is explicitly disabled in production mode, can I override this somehow? I have the same behavior on freebsd and OSX. For the heck of it I created a new rails app and had the same problem.

3

Here is a log entry in production:

Processing CategoriesController#index (for 127.0.0.1 at 2008-03-02 15:57:46) [GET]   Session ID: BAh7BzoMY3NyZl9pZCIlMDM0MDBmYzFmZmFhNzNkOWM3OWMyODE4Y2UzZTMw %0AZWEiCmZsYXNoSUM6J0FjdGlvbkNvbnRyb2xsZXI6OkZsYXNoOjpGbGFzaEhh %0Ac2h7AAY6CkB1c2VkewA%3D--3900448070a5ee4787c7a73043c9331d6e0388a3   Parameters: {"action"=>"index", "controller"=>"categories"} Rendering categories/index Completed in 0.25246 (3 reqs/sec) | Rendering: 0.00867 (3%) | DB: 0.00000 (0%) | 200 OK [http://localhost/categories\]

and in development:

Processing CategoriesController#index (for 127.0.0.1 at 2008-03-02 15:57:11) [GET]   Session ID: BAh7BzoMY3NyZl9pZCIlMDM0MDBmYzFmZmFhNzNkOWM3OWMyODE4Y2UzZTMw %0AZWEiCmZsYXNoSUM6J0FjdGlvbkNvbnRyb2xsZXI6OkZsYXNoOjpGbGFzaEhh %0Ac2h7AAY6CkB1c2VkewA%3D--3900448070a5ee4787c7a73043c9331d6e0388a3   Parameters: {"action"=>"index", "controller"=>"categories"}   SQL (0.000270) SET SQL_AUTO_IS_NULL=0   Category Load (0.000395) SELECT * FROM `categories`   Entry Load (0.055512) SELECT * FROM `entries` Rendering categories/index   Category Columns (0.002757) SHOW FIELDS FROM `categories` Completed in 0.25735 (3 reqs/sec) | Rendering: 0.00572 (2%) | DB: 0.05893 (22%) | 200 OK [http://localhost/categories\]

I'm baffled.

4

I copied development.rb to production.rb and still have the same problem. I suspect database timing is explicitly disabled in production mode, can I override this somehow? I have the same behavior on freebsd and OSX. For the heck of it I created a new rails app and had the same problem.

Well I've no idea why this is happening, but database timing certainly
isn't disabled in production.

Fred