- exception CacheConsistencyError#
Raised when we detect internal cache corruption, having to do with transactional consistency.
This is probably a transient error. By the time it is raised, the faulty cache will have been cleared, and we can try again.
- exception CacheCorruptedError#
Raised when we detect internal cache corruption, outside of any particular transaction.
- interface IGeneration#
A generation in a cache.
The maximim weight allowed.
The name of the generation
The number of the generation.
Iterate the ILRUEntry objects in this generation, from most recent to least recently used.
- interface IGenerationalLRUCache#
The cache moves items between three generations, as determined by an admittance policy.
Items begin in eden, where they stay until eden grows too large.
When eden grows too large, the least recently used item is then (conceptually) moved to the probation ring. If this would make the probation ring too large, the frequency of the least recently used item from the probation ring is compared to the frequency of the incoming item. Only if the incoming item is more popular than the item it would force off the probation ring is it kept (and the probation item removed). Otherwise the eden item is removed.
When an item in probation is accessed, it is moved to the protected ring. The protected ring is the largest ring. When adding an item to it would make it too large, the least recently used item is demoted to probation, following the same rules as for eden.
This cache only approximately follows its size limit. It may temporarily become larger.
The youngest generation.
The protected generation.
The probation generation.
Ordered list of generations, with 0 being NoSuchGeneration.
- interface ILRUCache#
A container of cached keys and values and associated metadata, limited to containing a total weight less than some limit.
The interface is mapping-like, and specified in terms of keys and values. For access to the additional stored metadata, different methods are defined.
Values may be evicted when new ones are added.
The cache may not store None values.
The cache may have specific restrictions on the type and format of keys and values it accepts.
The maximim weight allowed.
The weight of the entries in the cache.
Get a value by key. If there is no value for the key, or it has been evicted, return None.
This should be considered a hit on the key.
This never results in raising a KeyError.
Count how many entries are in the cache.
Is the key in the cache?
Iterate the keys
- __setitem__(key, value)#
Either set or update an entry.
If the key already existed in the cache, then update its
valueto the new value and mark it as the most recently used.
Otherwise, create a new entry for the key, setting it to the most recently used.
This may evict other items.
Remove the entry from the cache.
If it does not exist, it is an error.
__getitem__, but does not count as a hit on the key, merely returns a value if its present.
Iterate all the ILRUEntry values.
- add_MRUs(ordered_keys_and_values, return_count_only=False)#
Add as many of the key/value pairs in ordered_keys_and_values as possible, without evicting any existing items.
Returns the entries that were added, unless return_count_only is given, in which case it returns the count added instead. (This can save memory if the entries are not actually needed.)
Call to periodically adjust the frequencies of items.
- interface ILRUEntry#
An entry in an ILRUCache.
This is a read-only object. The containing cache is in charge of all the attributes, and they must not be changed behind its back.
The key for the entry
The value for the entry
The frequency of accesses to the entry.
The weight of the entry.
- interface IPersistentCache#
A cache that can be persisted to a location on disk and later re-populated from that same location.
The byte-size of the entries in the cache.
The upper bound of the byte-size that this cache should hold.
Save the cache to disk.
Restore the cache from disk.
Remove the cache from disk.
- interface IStateCache#
The methods we use to store state information.
This interface is defined in terms of OID and TID integers; implementations (such as memcache) that only support string keys will need to convert.
All return values for states return
We use special methods where possible because those are slightly faster to invoke.
Given an (oid, tid) pair, return the cache data (state_bytes, tid_int) for that object.
The returned tid_int must match the requested tid.
(oid, tid)pair isn’t in the cache, return None.
A special tid value of None means that the client doesn’t know the TID to ask for and wants the best available; they are then required to verify that the returned object is visible (that is, within the ranges of TIDs the MVCC state permits).
- get(oid_tid, peek=False)#
__getitem__(), but allows the caller to specify that this is a “peek” operation and shouldn’t affect any internal bookkeeping such as statistics or most/least recently used lists.
- __setitem__(oid_tid, state_bytes_tid)#
Store the state_bytes_tid (
(state_bytes, tid_int)) for the
Note that it does not necessarily mean that the key tid matches the value tid.
Also note that if the object has been deleted,
state_bytesmay be None.
Remove the data cached for the oid/tid pair.
If no data is cached, this should do nothing.
- set_all_for_tid(tid_int, state_oid_iter)#
Store the states for the
(state, oid_int)pairs under
The state_oid_iter is an iteable of
(state, oid_int, prev_tid_int)pairs; this method may choose to buffer a limited amount of those pairs before passing them on to the underlying storage in a bulk group.
As an iterable, state_oid_iter may be consumed multiple times.
Release external resources held by this object.
This object may not be usable after this.
Create an object sharing the same underlying data, but capable of operating independently, such as in a new thread.
This may return the same object.
Like close, but intended to be called on child objects created for MVCC using a
Clear cached data.
Remove all cached data for each of the oid integers in oids.
- interface IStorageCache#
A cache, as used by
Implementations do not have to be thread-safe. Use
new_instance()to get an object to use concurrently.
This cache is for current objects, as viewed at the
highest_visible_tidof this object or before. While it is possible to request older or newer revisions using
loadSerial, such accesses are less likely to produce cache hits.
Create a new object to be used concurrently.
If before is given, it is an integer TID, giving the maximum transaction that will be visible to this object (this only works correctly for history-preserving storages).
Failing to provide before for a historical connection will lead to consistency errors.
- interface IStorageCacheMVCCDatabaseCoordinator#
Specialized cache coordinator.
- poll(cache, conn, cursor)#
Poll for invalidations since the last taken state of the viewer.
Update the state of the viewer and update the global state maintained in this coordinator.
This should be the first thing done after the conn is opened or a transaction has begun: in fact, to ensure that the global state never accidentally goes backwards, no snapshot of the database should have been taken with the connection yet. The queries we execute in this method should establish the snapshot for the first time.
Return a dictionary with interesting keys and values about the global state of this object.