Posted by tjholowaychuk on November 15, 2007 at 1:45am
Refactor code
12% (4 votes)
Caching content
45% (15 votes)
Opcode Caching
21% (7 votes)
Load balancing server setup
6% (2 votes)
More ram / better server CPU etc
15% (5 votes)
Total votes: 33
Comments
None of the above
Actually, you listed several reasons, but as someone who does a lot of performance assessment, tuning and optimization, I have found one all encompassing reason. It is simple, and it is "it depends".
Before you decide to go through the trouble of refactoring code, you have to first identify that there is indeed a problem with the code. Before adding memory, you have to know that there is memory shortage, ...etc.
So, before you tune/optimize, diagnose first.
Drupal performance tuning, development, customization and consulting: 2bits.com
Personal blog: Baheyeldin.com
Drupal performance tuning, development, customization and consulting: 2bits.com, Inc..
Personal blog: Baheyeldin.com.
That is defiantly true, I am
That is defiantly true, I am curious to which people commonly end up resorting to. But I do agree!
vision media
350designs
Tj Holowaychuk
Vision Media - Victoria BC Web Design
Victoria British Columbia Web Design School
None of the above #2
There is usually alot of performance gain out of tuning the default OS & web server before even touching Drupal. You can get almost a 50% increase simply by turning off all the Apache modules that you don't use that are turned on by default.
A PHP Accelerator should also be on the list of 1st steps....
PHP Accelerator caches
PHP Accelerator caches opcode doesnt it? may be more to it than that I have not used it
Tj Holowaychuk
Vision Media - Victoria BC Web Design
Victoria British Columbia Web Design School
PHP Accelerator
Yes, it basically compiles the code and keeps the "exe" around - no more interpreting during execution.
HUGE increase in performance and a simple install that works for an entire server.
Doesn't replace writing good code....
OK... that captcha is REALLY annoying !