My Ruby on Rails application is consuming around 129 MB of memory.. is this normal?
I have around 3,000 unique visitors a day, i have no complex queries…
My users table has about 18k rows.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My Ruby on Rails application is consuming around 129 MB of memory.. is this normal?
I have around 3,000 unique visitors a day, i have no complex queries…
My users table has about 18k rows.
129MB doesn’t seem too excessive to me. What I find more important: does that number grow over time?
If it does, the problem is probably how much of your data set you are loading into memory on a request.
Check out this blog post.
In brief: instantiating too many active record objects is a place where Rails app’s memory footprint really grows.
If, in a request, you were to iterate over all 18k users for some reason, and worse, iterate over all of their posts (or whatever associations you have), you’d be instantiating a ton of objects, which (should) get cleared after the request, but Ruby doesn’t give the memory back to the system after it has been allocated.