Some brief thoughts on your observations of LAMP performance...
For me, the interesting thing is comparing LAMP to the architectural recommendations of proprietary equivalents with a similar architecture.
Proprietary systems almost always recommend more RAM and CPU horsepower. But not in the way you think - they increase it by demanding more machines!
One for the RDBMS, one for the web server, and so forth.
It's all in the name of scalability, apparently. Still, it's interesting to note that LAMP techies don't recommend this kind of infrastructure until you're getting tens of thousands of hits an hour, whereas their proprietary competition recommends it even if you're looking at an internal team or departmental level solution that will barely manage tens of thousands of hits per year...
The cynic in me thinks it's all about selling more licenses, but I'm assured by people with vendor qualifications that it's about scalability and performance.
The costs and the results, I think, speak for themselves.
Some brief thoughts on your observations of LAMP performance...
For me, the interesting thing is comparing LAMP to the architectural recommendations of proprietary equivalents with a similar architecture.
Proprietary systems almost always recommend more RAM and CPU horsepower. But not in the way you think - they increase it by demanding more machines!
One for the RDBMS, one for the web server, and so forth.
It's all in the name of scalability, apparently. Still, it's interesting to note that LAMP techies don't recommend this kind of infrastructure until you're getting tens of thousands of hits an hour, whereas their proprietary competition recommends it even if you're looking at an internal team or departmental level solution that will barely manage tens of thousands of hits per year...
The cynic in me thinks it's all about selling more licenses, but I'm assured by people with vendor qualifications that it's about scalability and performance.
The costs and the results, I think, speak for themselves.