As a shop that has been working in rails for some time and familiar with that workflow it is nice to have some light shed on the tools we are used to using with RoR being applied WordPress. I am looking forward to developing a similar system and measuring the results.
One thing I’ll say about the old “we can always add a new server”. You’re absolutely correct. Anyone who says this, as a default answer is likely speaking from their “idea”, rather than “experience”.
One machine I’m hosting for a client is doing 100K uniques/hour, with one unique consisting of 200+ objects served by Apache + many database transactions.
This is a garden variety $100/month machine with 32 threads + only 32G memory.
The real answer to most performance challenges is to hire someone who first refers to top + mytop + apache logs + mysqltuner.
Rule of thumb – “Tune what you got first.”
Oh and hire someone who can precisely answer the question, “Why is this server slow?”, with factual data, rather than ideas.
August 20, 2011 at 10:14 pm |
Nice video Mark. Scaling information is great to go over.
LikeLike
August 21, 2011 at 6:35 am |
Awesome talk. Thanks Mark!
LikeLike
November 1, 2011 at 10:05 pm |
As a shop that has been working in rails for some time and familiar with that workflow it is nice to have some light shed on the tools we are used to using with RoR being applied WordPress. I am looking forward to developing a similar system and measuring the results.
LikeLike
January 26, 2015 at 10:20 am |
Great discussion.
One thing I’ll say about the old “we can always add a new server”. You’re absolutely correct. Anyone who says this, as a default answer is likely speaking from their “idea”, rather than “experience”.
One machine I’m hosting for a client is doing 100K uniques/hour, with one unique consisting of 200+ objects served by Apache + many database transactions.
This is a garden variety $100/month machine with 32 threads + only 32G memory.
The real answer to most performance challenges is to hire someone who first refers to top + mytop + apache logs + mysqltuner.
Rule of thumb – “Tune what you got first.”
Oh and hire someone who can precisely answer the question, “Why is this server slow?”, with factual data, rather than ideas.
LikeLike