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

Re: [wp-hackers] Dashboard performance

  • To: wp-hackers@xxxxxxxxxxxxxxxxxxxx
  • Subject: Re: [wp-hackers] Dashboard performance
  • From: Roy Schestowitz <r@xxxxxxxxxxxxxxx>
  • Date: Fri, 05 May 2006 02:56:21 +0100
  • Delivery-date: Fri, 05 May 2006 02:56:22 +0100
  • Envelope-to: s@schestowitz.com
  • In-reply-to: <a491f91d0605041647s5643e9b0g467a02ff0a61bf92@mail.gmail.com>
  • References: <Pine.LNX.4.61.0605041906070.29977@tribal.metalab.unc.edu> <Pine.LNX.4.61.0605041912210.29977@tribal.metalab.unc.edu> <a491f91d0605041647s5643e9b0g467a02ff0a61bf92@mail.gmail.com>
  • User-agent: Internet Messaging Program (IMP) H3 (4.0.3)
___/ On Fri 05 May 2006 00:47:27 BST, [ Robert Deaton ] wrote : \___

On 5/4/06, John Joseph Bachir <jjb@xxxxxxxxxxx> wrote:
On Thu, 4 May 2006, John Joseph Bachir wrote:
> Couldn't this problem be fixed by putting certain parts of the Dashboard
> into an iframe?
Actually I think using object would be more appropriate.

Even more appropriate would be using the new cron system to keep the feeds up to date and never having the dashboard page itself load them, just load the cached object out of the database.

While I don't know the WP cron system properly, it sounds as though you suggest that each site pulls the feeds periodically. Wouldn't that raise the load on the local server and the servers holding the (remote) feeds significantly? All for a mere gain in terms of speed? Some Web-based feed readers have the tendency to do this, but it's expensive.

Best wishes,

Roy

--
Roy S. Schestowitz      | "Ping this IP, see if it responds the second time"
http://Schestowitz.com  |  GNU is Not UNIX  ¦     PGP-Key: 0x74572E8E
 2:50am  up 7 days  9:47,  14 users,  load average: 0.56, 0.61, 0.73
     http://iuron.com - proposing a non-profit search engine


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