tried new relic however it requires silver to do a web transaction view, which seems to be a minimum $100 monthly even if I only want to use it for 10 minutes...I bit expensive for a hobbyist programmer who just wants to get time response time log points in to delineate times spent in: rails generic code, authlogic, paperclip, database... I might try to work out how to put logging into these points myself first.
Any advice welcome on how/where to put logging code that would: a) be the first bit of rails code hit when the request comes in? b) first point called out to authlogic for authentication (perhaps this is just in the specific controller before the "before_filter :require_user" line, and one at end point? c) first point for paperclip call (would be just in the controller before teh "webfile = Webfile.find_by_path( search_path )" line perhaps)? d) point where all the above calls complete and the streaming of data back to the browser starts (perhaps just in the controller at the " send_file webfile.file.path , :type => webfile.file_content_type, :disposition => 'inline'" line)? On Dec 17, 4:36 am, greghauptmann <[email protected]> wrote: > Thanks > > * I'll try new relic then to get some more incite > * re authentication I'm using authlogic so in fact after initial > authentication it should use session cookies. However authlogic does > store sessions in database.. > * re number of images etc and mongrel cluster, I'm only testing with > one mongrel, however I am here looking at per request stats > * re authenticating via apache: if I knew how I could do this, bit > have it integrated with my apps user provioning I'd look at this. Any > leads here? I couldn't find anything when I looked. > > Thanks > > On Dec 17, 4:00 am, sax <[email protected]> wrote: > > > 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.
