network profile
| bio | website | |
|---|---|---|
| location | ||
| age | 34 | |
| visits | member for | 2 years, 2 months |
| seen | Oct 22 '12 at 17:26 | |
| stats | profile views | 31 |
|
Apr 29 |
awarded | Notable Question |
|
Jul 2 |
awarded | Favorite Question |
|
Feb 7 |
awarded | Good Question |
|
Jan 4 |
awarded | Popular Question |
|
Mar 6 |
awarded | Benefactor |
|
Mar 6 |
comment |
Refactoring Wordpress to improve memory performance Although I did not get an answer that would satisfy my original requirements, I think you are closest to providing an answer that might, one day, lead to reduced memory usage. Enjoy the bounty! |
|
Mar 6 |
revised |
Refactoring Wordpress to improve memory performance Added APC plot. |
|
Mar 6 |
revised |
Refactoring Wordpress to improve memory performance Added comparison of WP 3.0.4 and 3.1 |
|
Mar 3 |
awarded | Nice Question |
|
Mar 3 |
comment |
Refactoring Wordpress to improve memory performance I agree that WP has been fine-tuned for a long time. But I do not think it was fine-tuned to work on crappy hosting, with a particular mixture of plugins. I am curious to see how far can I push it. Even if the changes do not make it into the core, it is good to have a documented way of hacking the core if you think you must. |
|
Feb 28 |
comment |
Refactoring Wordpress to improve memory performance @scribu When you say "conditional loading", are you talking about autoloading, or actually loading code based on a condition? How much it hurts the speed? |
|
Feb 28 |
comment |
Refactoring Wordpress to improve memory performance @scribu It is on my list. Upgrade to 3.1, rerun the statistics. |
|
Feb 28 |
comment |
Refactoring Wordpress to improve memory performance I am going to give APC a try and see what happens. When I originally asked that question, I meant more than just opcode caching - I meant reusing the entire environment that WordPress builds - code + data. Memcached will help getting you the data faster, but you will still be cloning the data in the server memory. Now it seems that opcode caching would potentially take care of ~90% of all memory consumption. |
|
Feb 27 |
comment |
Refactoring Wordpress to improve memory performance @Dougal Campbell I started a bounty on this question, to see if we can hack at least this one instance of WordPress bad enough to get at least 30% memory consumption improvement now, relatively painlessly. It could inspire some of the future development. |
|
Feb 27 |
awarded | Promoter |
|
Feb 27 |
revised |
Refactoring Wordpress to improve memory performance Mentioned bounty |
|
Feb 27 |
comment |
Refactoring Wordpress to improve memory performance @Rarst Aaand I give up for today. The biggest gain I could identify is minimizing the amount of .php code being loaded. I need to study some more to figure out how to best achieve that. |
|
Feb 27 |
comment |
Refactoring Wordpress to improve memory performance @scribu And I was completely wrong the whole time. My optimizations have minimal effect, as most of the memory is eaten by loaded .php code. I updated the question and added more charts. |
|
Feb 27 |
revised |
Refactoring Wordpress to improve memory performance added 1193 characters in body |
|
Feb 27 |
comment |
Refactoring Wordpress to improve memory performance @scribu I might be on to something. The WP_Object_Cache clones an object on every cache hit. Every single time you call get_post with post number as input parameter (and this is done about 15 times in my case), PHP creates yet another clone of your entire post object. This eventually leads to the post being cloned three different times in the globals, during the runtime there are many more clones. I am working on a fix. |
