Are you re-checking authentication for each image? Could you find some way to authenticate only once for all of your resources? Perhaps use Basic or Digest authentication for your images, and then somehow tie the password to the current session? If you can remove unnecessary database hits, you may be able to shave off some ms. You may add a few ms for HTTP authentication, though, so I'd take a close look.
Are you using a mongrel cluster? If this is all going through one mongrel instance, it's only handling one request at a time. Switching to passenger may help, as it can spawn new instances to handle simultaneous requests (depending on settings and your server's memory). On Dec 16, 8:02 am, Hassan Schroeder <[email protected]> wrote: > On Tue, Dec 15, 2009 at 11:13 PM, greghauptmann > > <[email protected]> wrote: > > PS. On average each request is about 3000ms to 5000ms when being > > served by RoR (authlogic/paperclip), as opposed to about 160ms for the > > same content but put directly under /public. I'm using mongrel. > > You can get a lot more specifics about what's happening time-wise > by installing the NewRelic monitoring plugin (http://newrelic.com/). > > Highly recommended. > > -- > Hassan Schroeder ------------------------ [email protected] > twitter: @hassan -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
