A basic Varnish installation consist of Varnishing sitting in from of your web server (referred to as back-end), clients will interact solely with Varnish and never know there is a back-end web server (nor should they have access to the back end directly). When a request comes in to Varnish for a page that is being cached over a standard HTTP connection Varnish will either service this directly to the client (without sending a request to the back-end) from Varnish’s cache if exist or if not in cache will send a request to your web back-end over its TCP socket via an HTTP request...
cache
Drupal, Pressflow and Varnish Caching
Submitted by sandip on Mon, 04/26/2010 - 23:41Lots of useful varnish and caching tips...
MySQL Connection Management in PHP
Submitted by sandip on Thu, 01/14/2010 - 18:17This article is intended to highlight various basic topics concerning proper methods of handling connections to MySQL databases in PHP, guidelines for caching dynamic content, and a technique called "lazy loading". Hopefully by the end of the article you'll have learned how to combat a very widespread and potentially devastating scalability problem seen in an enormous number of PHP web applications...
BleachBit to cleanup unwanted files on your openSUSE
Submitted by susegeek on Fri, 04/17/2009 - 01:30BleachBit is a simple cool utility to delete unnecessary files on the systemt to free disk space. This includes application and browser cache, temporary fiiles and cookies. Among the many supported application files are Bash, Beagle, Epiphany, firefox, Adobe flash, java, KDE, openoffice,Opera, XChat, rpmbuild etc.