When I initially start up my server I have two thin processes running that are only about 200M in size. They slowly creep up a few megs an hour until now a week later they are at 400M and 300M respectively. I realize that my site (http://wlodb.com) has some intensive pages that take a couple seconds to render (most notably http://wlodb.com/compounds ) but I''m wondering if this is normal? I usually get about 500,000 page hits a month. Should I have a cronjob to restart my server processes once a week or should I just work on implementing some server side caching which should resolve the issue? thanks! -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
i guess nobody has as many problems as me. in general, do thin server processes normally keep growing and growing or do they cap out in size? -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
Scott Kulik wrote:> i guess nobody has as many problems as me. in general, do thin server > processes normally keep growing and growing or do they cap out in size?Mine don''t grow in size.. of course, mine arn''t 200mb. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
I would see if there are ways for you to implement caching ... but it also seems like there is maybe a memory leak within your code causing some problems. I''m not expert, but those are my thoughts. On Dec 9, 9:43 am, Scott Kulik <rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> When I initially start up my server I have two thin processes running > that are only about 200M in size. They slowly creep up a few megs an > hour until now a week later they are at 400M and 300M respectively. > > I realize that my site (http://wlodb.com) has some intensive pages that > take a couple seconds to render (most notablyhttp://wlodb.com/compounds > ) but I''m wondering if this is normal? I usually get about 500,000 page > hits a month. > > Should I have a cronjob to restart my server processes once a week or > should I just work on implementing some server side caching which should > resolve the issue? > > thanks! > -- > Posted viahttp://www.ruby-forum.com/.--~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Bobnation wrote:> I would see if there are ways for you to implement caching ... but it > also seems like there is maybe a memory leak within your code causing > some problems. I''m not expert, but those are my thoughts. > > On Dec 9, 9:43�am, Scott Kulik <rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>thanks for the replies. yea, i think there may be a memory leak. what do you think is the best way to narrow it down to a specific page? -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---