[wp-trac] Re: [WordPress Trac] #3155: Several "notice" messages in WP 2.1-alpha3

[WordPress Trac]

#3155: Several "notice" messages in WP 2.1-alpha3
-------------------------+--------------------------------------------------
 Reporter:  quix0r       |        Owner:  anonymous
     Type:  enhancement  |       Status:  new      
 Priority:  normal       |    Milestone:  2.1      
Component:  General      |      Version:  2.1      
 Severity:  major        |   Resolution:           
 Keywords:               |  
-------------------------+--------------------------------------------------
Comment (by quix0r):

 I leave the text below the line unchanged because I have written it before
 I have read the email... :-/

 So it is true that some PHP versions take longer because of malloc to
 create an empty variable than "handling" the undefined variable? I guess
 this is a "flaw" in PHP itself and the discussion shall not be held here.
 So I don't continue at this point. :-)

 Maybe the element cacher is useless or is a negative impact on performance
 (time for execusion). But what about my idea of caching SQL results?
 Please read the next below anyway. I have described it there more
 detailed. :-)

 The attached pprofp.log is a profile report of a vanilla 2.1-alpha3.
 --------------
 Hmmm... In my Intranet with no plugins installed it makes no difference to
 have the element cache enabled or disabled. In both cases I have an
 execution time around 0.20 secs. But I'm still not giving up to convince
 you. :-) ;-)

 I need some more plugins installed to test it more detailed.

 And the element cache is written for reducing function calls by caching
 the results of the functions (I will try to cache more than the above
 listing). It is definedly not a time-safer, "only" a call-safer cache.

 My first target with this cache where the functions which are always and
 everywhere on the blog used regardless if you post a comment, write a
 post, or just view the blog.

 My next target are time-consuming queries (have you seen my profiler-
 result?) by caching their results in local files. Surely the cache must be
 purged when the cached tables (which where extracted from the query
 string) got updated by INSERT, UPDATE or DELETE (ALTER and CREATE, of
 course too but this will not happen so often... ;-) ).

 The results of my profiler (I used Advanced PHP Debugger's "pprofp") did
 show all one thing: mysql_fetch_object() and other functions where the
 "heaviest" functions PHP has to execute.

 So my idea here was to cache the result to reduce usage of these heavy
 functions.

 You may want to check-out [http://blog.mxchange.org/2006/09/17/an-
 approach-for-a-faster-wordpress-powered-weblog/ my blog] for more
 informations who I want to handle this. :-) There you also find the
 original profiler output. Strange: After I fixed the "notice messages" the
 number of fucntion calls was recudes significantly. ... Hmmm.... :-?

-- 
Ticket URL: <http://trac.wordpress.org/ticket/3155>
WordPress Trac <http://wordpress.org/>
WordPress blogging software