I''m not sure if the subject line is aptly named however I''ve noticed something for some time. It seems if I''ve been away from the app for a while, it takes fffffffffoooooooooorrrrrever to load a page again or refresh. I''ve noticed this both with Webrick and Mongrel. Once I''m back again, doing things response time is fine. Wondering why there is such a long lag time. Something in the server perhaps ? Stuart -- http://en.wikipedia.org/wiki/Dark_ambient --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On Oct 14, 1:16 pm, "Dark Ambient" <sambi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I''m not sure if the subject line is aptly named however I''ve noticed > something for some time. > It seems if I''ve been away from the app for a while, it takes > fffffffffoooooooooorrrrrever to load a page again or refresh. > I''ve noticed this both with Webrick and Mongrel. Once I''m back again, doing > things response time is fine. Wondering why there is such a long lag time. > Something in the server perhaps ? > > Stuart > > --http://en.wikipedia.org/wiki/Dark_ambientOthers have noticed similar behavior. In fact, several people have been discussing this in the raleigh-rb mailing list. To quote Ryan Daigle on this one.. "So it appears that the solution is to make your app wildly successful to avoid any prolonged periods of inactivity..." The exact cause of this is unknown (to me anyway), but it has been suggested that either the ruby interpreter is being swapped in from virtual memory or that the entire virtual OS is. By any chance is your app on a shared host? _Kevin --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On 10/14/06, _Kevin <kevin.olbrich-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > Others have noticed similar behavior. In fact, several people have > been discussing this in the raleigh-rb mailing list. > > To quote Ryan Daigle on this one.. > "So it appears that the solution is to make your app wildly successful > to avoid any prolonged periods of inactivity..." > > The exact cause of this is unknown (to me anyway), but it has been > suggested that either the ruby interpreter is being swapped in from > virtual memory or that the entire virtual OS is. > > By any chance is your app on a shared host?No it''s not in production yet or on any other server. Just running server> on my machine. And although it probably doesn''t mean anything I installed > everything using InstantRails. My app however is on edgerails and defaults > to Mongrel.Anyway, interesting information Kevin since it sounds like this goes beyond just a local issue. Curious to know if it''s ever come up on this list before or not and if Rails-core has addressed this issue at all ? Right now the lag time is significant - I''d say it''s minutes, 4-5 + , which would be a really bad thing in production. Stuart --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On Oct 14, 2:12 pm, "Dark Ambient" <sambi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 10/14/06, _Kevin <kevin.olbr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > Others have noticed similar behavior. In fact, several people have > > been discussing this in the raleigh-rb mailing list. > > > To quote Ryan Daigle on this one.. > > "So it appears that the solution is to make your app wildly successful > > to avoid any prolonged periods of inactivity..." > > > The exact cause of this is unknown (to me anyway), but it has been > > suggested that either the ruby interpreter is being swapped in from > > virtual memory or that the entire virtual OS is. > > > By any chance is your app on a shared host?No it''s not in production yet or on any other server. Just running server > > > on my machine. And although it probably doesn''t mean anything I installed > > everything using InstantRails. My app however is on edgerails and defaults > > to Mongrel.Anyway, interesting information Kevin since it sounds like this goes beyond > just a local issue. Curious to know if it''s ever come up on this list > before or not and if Rails-core has addressed this issue at all ? > Right now the lag time is significant - I''d say it''s minutes, 4-5 + , which > would be a really bad thing in production. > > StuartSounds like you have other issues. The lag times I have heard discussed are on the order of several seconds, I think. It might be interesting to have the task manager open when you do this again and then note which processes are eating up all the CPU cycles. _Kevin --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On 10/14/06, _Kevin <kevin.olbrich-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > > > > On Oct 14, 2:12 pm, "Dark Ambient" <sambi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > On 10/14/06, _Kevin <kevin.olbr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > > > > Others have noticed similar behavior. In fact, several people have > > > been discussing this in the raleigh-rb mailing list. > > > > > To quote Ryan Daigle on this one.. > > > "So it appears that the solution is to make your app wildly successful > > > to avoid any prolonged periods of inactivity..." > > > > > The exact cause of this is unknown (to me anyway), but it has been > > > suggested that either the ruby interpreter is being swapped in from > > > virtual memory or that the entire virtual OS is. > > > > > By any chance is your app on a shared host?No it''s not in production > yet or on any other server. Just running server > > > > > on my machine. And although it probably doesn''t mean anything I > installed > > > everything using InstantRails. My app however is on edgerails and > defaults > > > to Mongrel.Anyway, interesting information Kevin since it sounds like > this goes beyond > > just a local issue. Curious to know if it''s ever come up on this list > > before or not and if Rails-core has addressed this issue at all ? > > Right now the lag time is significant - I''d say it''s minutes, 4-5 + , > which > > would be a really bad thing in production. > > > > Stuart > > Sounds like you have other issues. The lag times I have heard > discussed are on the order of several seconds, I think. > > It might be interesting to have the task manager open when you do this > again and then note which processes are eating up all the CPU cycles. > > _KevinRuby.exe was the big winner rising form 30,000K in mem usage to 217,920 when the page finally refereshed. Not sure if this is normal. My laptop isn''t the most powerful so that might be part of the problem Stuart --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On Oct 14, 6:25 pm, "Dark Ambient" <sambi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 10/14/06, _Kevin <kevin.olbr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > > On Oct 14, 2:12 pm, "Dark Ambient" <sambi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > On 10/14/06, _Kevin <kevin.olbr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > Others have noticed similar behavior. In fact, several people have > > > > been discussing this in the raleigh-rb mailing list. > > > > > To quote Ryan Daigle on this one.. > > > > "So it appears that the solution is to make your app wildly successful > > > > to avoid any prolonged periods of inactivity..." > > > > > The exact cause of this is unknown (to me anyway), but it has been > > > > suggested that either the ruby interpreter is being swapped in from > > > > virtual memory or that the entire virtual OS is. > > > > > By any chance is your app on a shared host?No it''s not in production > > yet or on any other server. Just running server > > > > > on my machine. And although it probably doesn''t mean anything I > > installed > > > > everything using InstantRails. My app however is on edgerails and > > defaults > > > > to Mongrel.Anyway, interesting information Kevin since it sounds like > > this goes beyond > > > just a local issue. Curious to know if it''s ever come up on this list > > > before or not and if Rails-core has addressed this issue at all ? > > > Right now the lag time is significant - I''d say it''s minutes, 4-5 + , > > which > > > would be a really bad thing in production. > > > > Stuart > > > Sounds like you have other issues. The lag times I have heard > > discussed are on the order of several seconds, I think. > > > It might be interesting to have the task manager open when you do this > > again and then note which processes are eating up all the CPU cycles. > > > _KevinRuby.exe was the big winner rising form 30,000K in mem usage to 217,920 > when the page finally refereshed. > Not sure if this is normal. My laptop isn''t the most powerful so that might > be part of the problem > > StuartI''d wager that that is fairly unusual. Not sure what would cause it tho... _Kevin --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On 10/14/06, _Kevin <kevin.olbrich-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > > > > On Oct 14, 6:25 pm, "Dark Ambient" <sambi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > On 10/14/06, _Kevin <kevin.olbr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > > > > > > > > On Oct 14, 2:12 pm, "Dark Ambient" <sambi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > On 10/14/06, _Kevin <kevin.olbr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > > Others have noticed similar behavior. In fact, several people > have > > > > > been discussing this in the raleigh-rb mailing list. > > > > > > > To quote Ryan Daigle on this one.. > > > > > "So it appears that the solution is to make your app wildly > successful > > > > > to avoid any prolonged periods of inactivity..." > > > > > > > The exact cause of this is unknown (to me anyway), but it has been > > > > > suggested that either the ruby interpreter is being swapped in > from > > > > > virtual memory or that the entire virtual OS is. > > > > > > > By any chance is your app on a shared host?No it''s not in > production > > > yet or on any other server. Just running server > > > > > > > on my machine. And although it probably doesn''t mean anything I > > > installed > > > > > everything using InstantRails. My app however is on edgerails and > > > defaults > > > > > to Mongrel.Anyway, interesting information Kevin since it sounds > like > > > this goes beyond > > > > just a local issue. Curious to know if it''s ever come up on this > list > > > > before or not and if Rails-core has addressed this issue at all ? > > > > Right now the lag time is significant - I''d say it''s minutes, 4-5 + > , > > > which > > > > would be a really bad thing in production. > > > > > > Stuart > > > > > Sounds like you have other issues. The lag times I have heard > > > discussed are on the order of several seconds, I think. > > > > > It might be interesting to have the task manager open when you do this > > > again and then note which processes are eating up all the CPU cycles. > > > > > _KevinRuby.exe was the big winner rising form 30,000K in mem > usage to 217,920 > > when the page finally refereshed. > > Not sure if this is normal. My laptop isn''t the most powerful so that > might > > be part of the problem > > > > Stuart > > I''d wager that that is fairly unusual. Not sure what would cause it > tho... > > _KevinKevin , are you saying that Ruby is taking too much memory ? I have the task manager open and it''s staying in that range. Stuart --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On Oct 14, 7:12 pm, "Dark Ambient" <sambi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 10/14/06, _Kevin <kevin.olbr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > > On Oct 14, 6:25 pm, "Dark Ambient" <sambi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > On 10/14/06, _Kevin <kevin.olbr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > On Oct 14, 2:12 pm, "Dark Ambient" <sambi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > On 10/14/06, _Kevin <kevin.olbr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > > Others have noticed similar behavior. In fact, several people > > have > > > > > > been discussing this in the raleigh-rb mailing list. > > > > > > > To quote Ryan Daigle on this one.. > > > > > > "So it appears that the solution is to make your app wildly > > successful > > > > > > to avoid any prolonged periods of inactivity..." > > > > > > > The exact cause of this is unknown (to me anyway), but it has been > > > > > > suggested that either the ruby interpreter is being swapped in > > from > > > > > > virtual memory or that the entire virtual OS is. > > > > > > > By any chance is your app on a shared host?No it''s not in > > production > > > > yet or on any other server. Just running server > > > > > > > on my machine. And although it probably doesn''t mean anything I > > > > installed > > > > > > everything using InstantRails. My app however is on edgerails and > > > > defaults > > > > > > to Mongrel.Anyway, interesting information Kevin since it sounds > > like > > > > this goes beyond > > > > > just a local issue. Curious to know if it''s ever come up on this > > list > > > > > before or not and if Rails-core has addressed this issue at all ? > > > > > Right now the lag time is significant - I''d say it''s minutes, 4-5 + > > , > > > > which > > > > > would be a really bad thing in production. > > > > > > Stuart > > > > > Sounds like you have other issues. The lag times I have heard > > > > discussed are on the order of several seconds, I think. > > > > > It might be interesting to have the task manager open when you do this > > > > again and then note which processes are eating up all the CPU cycles. > > > > > _KevinRuby.exe was the big winner rising form 30,000K in mem > > usage to 217,920 > > > when the page finally refereshed. > > > Not sure if this is normal. My laptop isn''t the most powerful so that > > might > > > be part of the problem > > > > Stuart > > > I''d wager that that is fairly unusual. Not sure what would cause it > > tho... > > > _KevinKevin , are you saying that Ruby is taking too much memory ? I have the > task manager open and it''s staying in that range. > > StuartOn my machine (an Intel Mac), my ruby process only uses about 35MB + about 65MB of virtual memory. Not sure how well you can compare a PC to a Mac in terms of memory usage, but I can''t imagine that it would be normal to go from 30MB to 200+ in a single call. Unless you are doing something like creating an entire table worth of objects in a single call. _Kevin --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---