Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you post the contents of the log as that first request is processed then perhaps we can figure out what's making it so slow. For example, this is my log as the first user accesses the site </p> <pre><code>Booting Mongrel (use 'script/server webrick' to force WEBrick) Rails 2.1.0 application starting on http://0.0.0.0:3000 Debugger enabled Call with -d to detach Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.0/lib/action_controller/mime_type.rb:66: warning: already initialized constant CSV ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM =&gt; stop. USR2 =&gt; restart. INT =&gt; stop (no restart). ** Rails signals registered. HUP =&gt; reload (without restart). It might not work well. ** Mongrel 1.1.5 available at 0.0.0.0:3000 ** Use CTRL-C to stop. Processing SessionsController#new (for 127.0.0.1 at 2009-05-26 12:26:00) [GET] Session ID: de2acf074759026e1ed6205724f547a9 Parameters: {"action"=&gt;"new", "controller"=&gt;"sessions"} Rendering sessions/new Completed in 0.00587 (170 reqs/sec) | Rendering: 0.00298 (50%) | DB: 0.00092 (15%) | 200 OK [http://localhost/] </code></pre> <p>I think 170 reqs/sec is fine for our app but others may find that slow. You can see from the stats that rails provides that half of the time required is spent rendering the response - in this case generating the HTML for the login screen. If this request was taking a long time, my first port of call would be the views and helpers associated with the login screen.</p> <p>If you do have a system that takes a long time to initialize itself on the very first request then why not be sneaky and write your own startup program which first runs rails and then sends a fake request in via curl. That way your users never see the problem.</p> <p>Chris</p>
    singulars
    1. This table or related slice is empty.
    1. POFirst request to Rails app is very slow
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USChris McCauley
    1. USChris McCauley
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POFirst request to Rails app is very slow
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for your hint. Here is my logfile: http://pastie.org/private/ih2mpcmjpofp5jmfsvw Sometimes, it lasts much longer than 1600 ms to answer my request. I really don't have a clue...
      singulars
      1. PO
      1. USStefan
    2. COWhat version of rails are your using? Completed in 10367ms (View: 1572, DB: 450) | 200 OK [http://localhost/search?search=stefan+] It looks like it's taking 10 seconds to answer the first request. I guess that searching again for the same query "stefan" is much faster? How long does it take to find a different record? Finally how long does it take to search for a non-existant record?
      singulars
      1. PO
      1. USChris McCauley
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload