<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sat, 25 May 2013 16:55:22 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPClasses.org Blog: Throttling Background Tasks: Unusual Site Speedup Techniques: Part 2]]></title>
      <guid>http://www.phpdeveloper.org/news/15334</guid>
      <link>http://www.phpdeveloper.org/news/15334</link>
      <description><![CDATA[<p>
On the PHPClasses.org blog <i>Manuel Lemos</i> has <a href="http://www.phpclasses.org/blog/post/132-Accelerate-Page-Accesses-Throttling-Background-Tasks-Unusual-Site-Speedup-Techniques-Part-2.html">posted part two</a> of his look at techniques to help speed up your site - a few things that you maybe hadn't thought of before.
</p>
<blockquote>
In the <a href="http://www.phpclasses.org/blog/post/131-Accelerate-Page-Loading-Unusual-Site-Speedup-Techniques-Part-1.html">previous article</a> I talked about one important factor that often seriously affects the user perception of the speed of a site, which is the presence of content from external sites that slows down the load of pages, such as advertising and widgets. In that article I presented a technique that I am using to make external content not affect the user perception of the site speed. In this article I am addressing another factor that may also affect the user perception of site speed, but this time is related to aspects of the server side environment.
</blockquote>
<p>
In this article he looks at things like other server-side background processes, throttling their CPU usage, throttling PHP's CPU usage and the use of <a href="http://www.phpclasses.org/system-monitor">a monitoring class</a> to help you and your applications (and sysadmins) stay on top of what's happening with the server.
</p>]]></description>
      <pubDate>Tue, 26 Oct 2010 09:17:55 -0500</pubDate>
    </item>
  </channel>
</rss>
