Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Mon, 31 Jul 2006 18:47:55 -0000
Message-ID: <20060731184755.748.48935@ajax.apache.org>
Subject: [Db-derby Wiki] Update of "DerbyLruCacheManager" by
 GokulSoundararajan

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by GokulSoundararajan:
http://wiki.apache.org/db-derby/DerbyLruCacheManager

------------------------------------------------------------------------------
   1. '''CLOCK-Pro: an effective improvement of the CLOCK replacement''' - Song Jiang, Feng Chen, and Xiaodong Zhang [http://www.cs.wm.edu/hpcs/WWW/HTML/publications/papers/TR-05-3.pdf Link]
  
  == Status/Updates ==
+ 
+ === July 31, 2006 ===
+ 
+ With some simple code changes, I modified the mirrored cache implementation to have almost no overhead (only 1% now).
+ I have posted the results of my Zipf workload that I execute through the {{{T_CacheService}}} unit test. I'm using an approximation to ClockPro which gives pretty good performance. It is comparable to my earlier results that I got from simulation. The ClockPro approximation is like 2Q but the LRU lists are replaced with Clock. This avoids the overhead of shifting items to the top of the stack. I'll post more details later.
+ 
+ See the results of the mirrored cache implementation compared to the original Clock already in Derby.
+ 
+ Graphs:
+ [http://www.eecg.toronto.edu/~gokul/soc/final-impl-results.png PNG]
+ [http://www.eecg.toronto.edu/~gokul/soc/final-impl-results.pdf PDF]
+ 
  
  === July 21, 2006 ===