Ruby and rails perfomance issue, server -

I am running a stationary rail webserver, and I am facing memory issues, I have an error: ENSOM error Every time I try to invite sendmail, when I run the 'top' on my server, it shows me that 2 ruby1.8 processes are going on, each digestive memory has about 40% memory. Is this caused by a leak in my code, or have I launched two parallel Ruby processes?

Both processes are run by my recruitment account, and after that when I push my production GIT repository (using Pushand) I am trying to figure out whether it is natural (I.e. need to upgrade the server) or if I have any mistake in my setup I have upgraded my RAM from 256 MB to 512 MB, and before that it was not a problem.

The problem is preventing visitors from making a user, because the application throws an error when they should receive an activation email.

Note that I am running Rail 2.1.0 on an Ubuntu setup, with the Apache and passenger.

OK, I think it was one of those cases where I helped myself Had had had, and I was really happy that I did. I did not use any of the tools I had linked.

I have logged into my server Ssh and two commands run in two screen windows: top and tail -f /var/www/mysite.com/log/production.log.

I looked at the live log file and took a long time to load a page request saw ?? A page where a user can show his images, where each user is identified with their name. Acts_as_taggable_on It took 6 seconds for a single request.

And it kept popping up. I think I saw it 6 or 7 times, and I decided to check it further. It was always the same user id, so I decided to look at the user. It has been learned that the user has an empty name, "", and tagged images

  Asset.tagged_with (@ user.name ,: on => "user") < / Now in my app, there are thousands of assets, and Asset.tagged_with ("",: = on = "users") will return to all of them, thus my eatable memory  
 Now I have handled the case where a user has an empty name, and it is necessary for all new users even if no one helped, even though I still feel some gratitude towards StackHoverflow Because sometimes it is as simple as asking questions to solve its problem.