Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: [wp-hackers] Dashboard performance

On 5/4/06, Roy Schestowitz <r@xxxxxxxxxxxxxxx> wrote:
...Yet  it  comes to show the deficiency of caching. Check too  frequently
and hog resources; check infrequently and present out-of-date information.

We already cache.

As to other ideas: data prefetching for feeds,

This would be the point of the cron, the data would be prefetched and not on page load.
use of stylehseet to alter
the  order/flow  of content and thus the order in which file requests  are
made  in  most  Web browsers. There are several such  subtle  optimisation
tricks.

We've talked about these things in the past and they are not a solution, and cannot be in a software like WordPress, there are too many outside factors to consider:

-Things like mod_gzip, which have their own buffer inside apache, and
won't send to the browser until the page is done loading.
-The adverse performance effects of flush(), its unreliability on
certain PHP SAPIs
-etc.


Best wishes,

Roy

--
Roy S. Schestowitz      |    Useless fact: Every polar bear is left-handed
http://Schestowitz.com  |    SuSE Linux     Â     PGP-Key: 0x74572E8E
  3:20am  up 7 days 10:17,  14 users,  load average: 0.49, 0.60, 0.68
      http://iuron.com - Open Source knowledge engine project

_______________________________________________
wp-hackers mailing list
wp-hackers@xxxxxxxxxxxxxxxxxxxx
http://lists.automattic.com/mailman/listinfo/wp-hackers



--
--Robert Deaton
http://somethingunpredictable.com
_______________________________________________
wp-hackers mailing list
wp-hackers@xxxxxxxxxxxxxxxxxxxx
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index