Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We moved any calls that could take longer than one or two seconds to a prioritized queue to be processed asynchronously. We use <a href="http://github.com/collectiveidea/delayed_job" rel="nofollow noreferrer">delayed_job (the collectiveidea branch)</a> to handle all background jobs, but another that is getting popular these days is <a href="http://github.com/defunkt/resque" rel="nofollow noreferrer">resque</a>, I have not used it and cannot speak to it other that its basic function.</p> <p>From there you can use ajax to poll the status of the job while you show a progress bar or a spinner or a can eating a baked potato - until the job finishes. This way the background job processes in the background and your web front end will remain snappy.</p> <p>The flow would be:</p> <ol> <li>User submits Request</li> <li>Request Queued</li> <li>Front end responds</li> <li>Network operation starts</li> <li>Network operation ends</li> <li>Begin polling at customer</li> <li>Background job finished</li> <li>Poll gets response and updates UI</li> </ol> <p>VS.</p> <ol> <li>User submits Request</li> <li>Network operation starts</li> <li>Network operation ends</li> <li>Front end responds</li> </ol> <p>This is a bit more complicated than your standard fare of get/process/display but when you have long-running processes, this is the desired method of handling them. An example in the wild of this is Mint.com. When it updates your bank accounts you can click all over the site and when it is done, you are notified.</p> <p>If you are unable to go this route then you are just going to need to increase the number of processes on your front end to handle incoming requests. We are migrating to <a href="http://github.com/defunkt/unicorn" rel="nofollow noreferrer">unicorn</a> but <a href="http://www.modrails.com/" rel="nofollow noreferrer">passenger</a> should be effective in making sure that your busy workers do not get new requests. I recommend this only as a last resort - your requests should all respond in a second or at the most two and everything else should go to a background job processor.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to make Rails Nonblocking?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USGeoff Lanotte
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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