When running DSL as a desktop, my memory usage rarely hits 96megs (with FF and terminal open), yet my ubuntu servers all running LAMP stacks will hit 128mb whith no traffic (when traffic does pickup, they will reach into the 500+ meg area).

Are there any gotchas with using damn small linux as a web server?


Well first off you're comparing the memory usage of DSL desktop running FF and a terminal to a server running MySQL and multiple Apache processes. When you say 500mb does that include the cache? Linux will use all the memory available as unused memory is wasted memory. So if you have 512mb of ram in the system I would expect it to hit around 500mb of used memory eventually. It will leave some free for memory allocations for dealing with interrupts and the like. I believe that you'll find that running a LAMP stack on DSL will have similar memory usage compared to Ubuntu Server.

Beyond that I would be concerned about how manageable DSL would be in the long run. I'm not sure what DSL's repositories and package management is like so I won't compare it to Ubuntu. But a quick look at DSL's wiki seems to imply that you need compile from source. Where Ubuntu Server has a solid LTS for easy security updates and huge repositories for any other libraries or applications you may need as well as dealing with any dependencies.

If this is for a business think of the person who may replace you one day. Finding someone familiar/comfortable with running web servers running CentOS, Ubuntu, or RHEL will be much easier than finding someone who is as familiar/comfortable with running one on DSL.

| improve this answer | |
  • Your comment reminded me of this site: linuxatemyram.com A great explanation of why linux hasn't eaten all your RAM – Twirrim Feb 12 '10 at 1:34

You're really comparing apples with oranges here. Apache is a memory hog, as it spawns new processes to handle incoming connections due to the way it's designed (off the top of my head I believe every Apache instance in a fairly stock Ubuntu install comes to around 15Mb).

If you want to cut down on memory usage, you could try switching over to nginx or lighttpd which don't work the same way, don't spawn lots of processes and have a much lighter memory footprint. A significant number of major websites have transitioned over to such alternatives from Apache, and are reaping the benefits. My preference is towards nginx rather than lighttpd these days.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.