rubyonrailsin

Thanks all.  The amount of data on the Ubuntu staging server is a little bit more than the data on my Leopard laptop.  So the slight difference in DB access time seems reasonable.  What worries me is the intolerably long time the Ubuntu machine takes to produce the views.  I also notice that the ruby1.8 process on Ubuntu briefly shots up close 100% of the CPU during that time.  Below are the specs of the computers

1. Snow Leopard Laptop :  MacBook Pro 2.53 GHz Intel Core 2 Duo, 4GB 1067 MHz DDR3, 250.06 GB SATA hard drive
• ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]
• Rails 2.3.5
• mysql  Ver 14.14 Distrib 5.1.43, for apple-darwin10.2.0 (i386) using readline 5.1
• Mongrel
  
  
2. Ubuntu 9.10 Server (old former custom built Windows xp computer):  Intel Pentium 4 3.00 Ghz, 1G RAM, 18 (eighteen) GB hard drive. (IDE), 855 MB is swap partition.
   

• ruby 1.8.7 (2009-06-12 patchlevel 174) [i486-linux]
• Rails 2.3.5
• mysql  Ver 14.14 Distrib 5.1.37, for debian-linux-gnu (i486) using  EditLine wrapper
• apache2

Could the difference in hardware configuration explain the slowness in the Ubuntu box? 

>> On my Leopard, I get: Completed in 643ms (DB: 322) | 302 Found
>> For Ubuntu, I get:     Completed in 8803ms (DB: 517) | 302 Found