<?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>Wed, 22 May 2013 09:42:03 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Andrew Martin's Blog: Serving PHP session files from a RAM based disk (tmpfs) for AWS Micro Instance]]></title>
      <guid>http://www.phpdeveloper.org/news/16959</guid>
      <link>http://www.phpdeveloper.org/news/16959</link>
      <description><![CDATA[<p>
<i>Andrew Martin</i> has a new post to his blog looking at a technique that could be used to help minimize some of the performance issues you could see on <a href="http://aws.amazon.com">AWS micro instances</a> dealing with PHP session handling. His alternative is <a href="http://www.binarysludge.com/2011/08/31/serving-php-session-files-from-a-ram-based-disk-tmpfs-for-aws-micro-instances/">serving them from a RAM-based disk</a> instead.
</p>
<blockquote>
It's rare to find a web server with slow disk I/O performance, but Amazon's EC2 micro-instances are one such example. Their EBS disk subsystem access is rated "low", and this can have a detrimental effect on HTTP throughput. [...] This leaves sessions, which can be written to a <a href="http://www.binarysludge.com/2011/01/13/redundant-and-fault-tolerant-php-session-storage/">redundant and fault tolerant storage system</a>. [...] In order to speed up the disk access, a RAM-based disk can be mounted over the session directory. This has the disadvantage of being volatile - the data is lost in case of a server reboot, or the mount point being unmounted. However if tolerable, storing sessions in RAM insulates the application from poor filesystem performance.
</blockquote>
<p>
He mentions the two types of kernels that can be used, ramfs and tmpfs, and the specifics of using a tmpfs filesystem to implement the technique (complete with command line calls to make it happen). 
</p>]]></description>
      <pubDate>Thu, 06 Oct 2011 11:42:36 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Chris Jones' Blog: Reducing diskspace of your Oracle Instant Client install]]></title>
      <guid>http://www.phpdeveloper.org/news/12312</guid>
      <link>http://www.phpdeveloper.org/news/12312</link>
      <description><![CDATA[<p>
<i>Chris Jones</i> has <a href="http://blogs.oracle.com/opal/2009/04/reducing_diskspace_of_your_ora.html">a recommendation</a> for those compiling Oracle support into PHP - there's a simple way to reduce the amount of disk space that your Instant Client install uses - a "only what's needed" setup.
</p>
<blockquote>
Most PHP OCI8 users link PHP with the <a href="http://www.oracle.com/technology/tech/oci/instantclient/index.html">Oracle Instant Client</a> (IC) libraries that handle the underlying "client" (i.e PHP OCI8 extension) communication with the database. IC is relatively small for the features it gives, and is very easy to install. A ZIP or RPM download unpacks a few libraries. [...] Although IC isn't particularly big - and it's getting relatively smaller all the time - there are two ways to reduce its size.
</blockquote>
<p>
His two recommendations are to use the lite client version instead of the full-blown one (only has common character sets) or you can just remove the JDBC/ODBC/OCCI libraries from the full install. He lists out the files that are actually needed by the OCI8 extension to compile correctly.
</p>]]></description>
      <pubDate>Thu, 09 Apr 2009 10:29:16 -0500</pubDate>
    </item>
  </channel>
</rss>
