1. 12 Oct, 2005 1 commit
  2. 05 Oct, 2005 3 commits
  3. 04 Oct, 2005 3 commits
  4. 03 Oct, 2005 2 commits
  5. 25 Sep, 2005 1 commit
  6. 06 Sep, 2005 2 commits
  7. 26 Aug, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 38114 from trunk. · 72795b10
      Tim Peters authored
      Collector 1873.
      
      update_from_seq():  If PySequence_Check(seq) returns true,
      go on to check for the existence of "iteritems" when deciding
      whether the input is or is not "a sequence".  Alas,
      PySequence_Check() does return true for PersistentMapping and
      PersistentDict instances, so that they couldn't be used as
      arguments to BTree/Bucket construction or update().
      
      This is nasty type-sniffing, but it was before too.  There's
      no way to make such stuff bulletproof, so I'm settling for
      incremental improvement.
      72795b10
  8. 25 Aug, 2005 1 commit
  9. 24 Aug, 2005 1 commit
  10. 23 Aug, 2005 1 commit
  11. 12 Aug, 2005 1 commit
  12. 09 Aug, 2005 1 commit
  13. 08 Aug, 2005 3 commits
  14. 07 Aug, 2005 2 commits
  15. 04 Aug, 2005 3 commits
    • Tim Peters's avatar
      An internal 3.4.1b3 release. · fc43960e
      Tim Peters authored
      fc43960e
    • Tim Peters's avatar
      Plug leaks in the ZEO client cache. · 27464d77
      Tim Peters authored
      ClientCache._evicted():  When deleting the last range of
      non-current tids for an oid, remove the list from the
      noncurrent dict instead of leaving an empty list sitting
      there forever.  This also required adjusting the side-
      effect dance in ClientCache._remove_noncurrent_revisions().
      
      FileCache._makeroom():  This was the major leak -- it
      neglected to remove an evicted object's Entry from the
      key2entry dict.
      27464d77
    • Philipp von Weitershausen's avatar
      Merge r37707 from the trunk: · ceaf402f
      Philipp von Weitershausen authored
        Merge the philikon-zeo-scripts branch:
          move things around so that zeo scripts are installed for
          standalone zodb releases but not for zope releases
      ceaf402f
  16. 02 Aug, 2005 1 commit
  17. 01 Aug, 2005 2 commits
  18. 29 Jul, 2005 2 commits
    • Tim Peters's avatar
      7f94c939
    • Tim Peters's avatar
      Removed the `key2size` OIBTree. · 5664b307
      Tim Peters authored
      Maintaining this is a significant expense; the code didn't
      make real use of it; and every time I've tried to exploit it
      I've ended up with grossly too-large simulated hit rates.
      Would probably take another day to figure out exactly why that
      is, and the simulated rates are "good enough" now without it.
      5664b307
  19. 26 Jul, 2005 4 commits
    • Tim Peters's avatar
      An internal 3.4.1b1 release. · 8a4983e8
      Tim Peters authored
      8a4983e8
    • Tim Peters's avatar
      More words; update examples w/ new output. · 04d1d290
      Tim Peters authored
      04d1d290
    • Tim Peters's avatar
      The cache simulation seems good enough to be useful now, · b2d53a75
      Tim Peters authored
      although the toy app I wrote to generate a 500MB trace
      file doesn't use MVCC in an essential way (some of the
      MVCC simulation code is nevertheless exercised, since
      an invalidation of current data in the presence of MVCC
      always creates a cache record for the newly non-current
      revision).
      
      Still puzzling over what to do when the trace file records
      a load hit but the simulated cache gets a miss.  The
      old simulation code seemed to assume that a store for the same
      oid would show up in the trace file next, and it could get
      the info it needed about the missing object from the store
      trace.  But that isn't true:  precisely because the load was
      a hit in the trace file, the object isn't going to be stored
      again "soon" in the trace file.
      
      Here are some actual-vs-simulated hit rate results, for a
      20MB cache, with a trace file covering about 9 million
      loads, over 3 ZEO client (re)starts:
      
      actual   simulated
      ------   ---------
        93.1        92.7
        79.8        79.0
        68.0        69.1
            
        81.4        81.1  overall
      
      Since the simulated hit rates are both higher and lower
      than the actual hit rates, that argues against a gross
      systematic bias in the simulation (although there may
      be several systematic biases in opposite directions).
      b2d53a75
    • Tim Peters's avatar
      Massive rewrite to make simul.py's circular cache aware of · 9c47277a
      Tim Peters authored
      MVCC.  It isn't blowing up, but it thinks the hit rate is
      100% -- might have missed something there <wink>.
      9c47277a
  20. 25 Jul, 2005 1 commit
    • Tim Peters's avatar
      More steps on the way toward having useful cache simulation. · 15bb2e12
      Tim Peters authored
      I think the primary hangup now is that simul.py doesn't know
      anything about MVCC.  As a result, it thinks there's significatly
      more free space in the cache than there really is, and that
      probably accounts for it predicting significantly higher hit
      rates than I actually see.
      15bb2e12
  21. 23 Jul, 2005 1 commit
  22. 22 Jul, 2005 3 commits