Skip to content

Internalize heap-size tracking into Tsavorite#1712

Merged
badrishc merged 27 commits intodevfrom
badrishc/replace-subscribe-eviction
Apr 19, 2026
Merged

Internalize heap-size tracking into Tsavorite#1712
badrishc merged 27 commits intodevfrom
badrishc/replace-subscribe-eviction

Conversation

@badrishc
Copy link
Copy Markdown
Collaborator

@badrishc badrishc commented Apr 17, 2026

Summary

Replaces Garnet's heavyweight SubscribeEvictions observer pattern with Tsavorite-internal heap-size accounting. Previously, Garnet wired LogSizeTracker as an IObserver<ITsavoriteScanIterator> via SubscribeEvictions, which materialized a full page iterator on every eviction to sum heap sizes. Session functions (ISF) were responsible for creation-site, destruction-site, and in-place-mutation heap tracking, requiring every ISF implementation to manually call cacheSizeTracker.AddHeapSize() — fragile and error-prone.

Now, Tsavorite owns the complete heap-size lifecycle with zero ISF involvement:

Accounting Who How
+key at record creation Tsavorite CAS success sites (InternalRMW/Upsert/Delete)
+value at record creation Tsavorite After Post{InitialUpdater,InitialWriter,CopyUpdater} callbacks
+value on revivification Tsavorite In-chain revivification (InternalRMW/Upsert)
±delta on in-place update Tsavorite Pre/post GetValueHeapMemorySize() around InPlaceUpdater/Writer
−value on delete Tsavorite OnDispose(Deleted) — before tombstone is set
−value on copy-update Tsavorite OnDispose(CopyUpdated) — source cleared after copy
−(key+value) on eviction Tsavorite EvictRecordsInRange per-record walk
−key on tombstone eviction Tsavorite EvictRecordsInRange (value already subtracted at delete)
−remaining on elide/freelist Tsavorite OnDispose(Elided/RevivificationFreeList)

What Changed

Tsavorite core (libs/storage/Tsavorite/):

  • InternalRMW.cs — IPU: pre/post GetValueHeapMemorySize() around InPlaceUpdater (including ExpireAndStop path). CAS success: +key after CAS, +value after PostInitialUpdater/PostCopyUpdater. In-chain revivification: +value. CopyUpdated disposal: −value + Dispose. ReinitializeExpiredRecord: +value.
  • InternalUpsert.cs — IPW: pre/post GetValueHeapMemorySize() around InPlaceWriter. CAS success: +key, +value after PostInitialWriter. Revivification: +value.
  • InternalDelete.cs — Mutable delete: OnDispose(Deleted) before SetTombstone(). CAS success: +key only (value becomes inline tombstone).
  • ObjectAllocatorImpl.csOnDispose: −value for Deleted, −(key+value) for Elided/RevivificationFreeList, no-op for CASFailed/InsertAbandoned. EvictRecordsInRange: per-record −(key+value) for live, −key for tombstoned; sealed records visited (not skipped).
  • IRecordTriggers.cs — New interface with DIM defaults: CallOnFlush/CallOnEvict/CallOnDiskRead (all default false), OnEvict(ref LogRecord, EvictionSource), OnFlush(ref LogRecord), OnDiskRead(ref LogRecord), OnDispose(ref LogRecord, DisposeReason), OnDisposeDiskRecord(ref DiskLogRecord, DisposeReason).
  • LogSizeTracker.cs — Removed IObserver<ITsavoriteScanIterator> implementation (OnNext/OnCompleted/OnError).
  • LogAccessor.csSubscribeEvictions no longer auto-wires logSizeTracker.
  • AllocatorBase.cs — Added IsReadCache field for EvictionSource routing.
  • EvictionSource.cs — New enum: MainLog, ReadCache.

Garnet server (libs/server/):

  • IGarnetObject.Operate — Removed out long sizeChange parameter. All implementations updated (Hash, List, Set, SortedSet, CustomObjectBase). Tsavorite now handles heap deltas internally.
  • GarnetRecordTriggers.cs — Empty readonly struct relying entirely on DIMs (no fields, no methods). Garnet objects hold no external resources requiring app-level cleanup.
  • ObjectStore/RMWMethods.cs — Removed all cacheSizeTracker.AddHeapSize() calls. HasRemoveKey path now simply sets ExpireAndStop without manual delta tracking.
  • MainStore/RMWMethods.cs — Removed inline guard and cacheSizeTracker calls (Tsavorite handles IPU delta).
  • SessionFunctionsUtils.cs — Removed GetValueHeapMemorySize pre/post delta tracking from TryCopyAndUpdateOverflowValue.
  • UnifiedStore/RMWMethods.cs — Removed out sizeChange plumbing.
  • ObjectStore/ReadMethods.cs — Updated Operate call (removed out _).

Removed patterns:

  • OnDisposeValueObject callback and disposer lambdas threaded through DiskLogRecord, ObjectIdMap, scan iterators
  • LogSizeTracker as IObserver<ITsavoriteScanIterator> (was the SubscribeEvictions consumer)
  • SubscribeEvictions auto-wire of logSizeTracker in LogAccessor
  • cacheSizeTracker.AddHeapSize() calls from all ISF implementations
  • IGarnetObject.Operate out sizeChange parameter and per-object previousMemorySize/memorySizeChange tracking

Key Invariants

Invariant Mechanism
Tombstone AFTER OnDispose OnDispose(Deleted) reads GetValueHeapMemorySize() before SetTombstone() zeroes it
Inline guard on IPU/IPW !preInline || !postInline check — skips heap measurement for the common inline-value path
Sealed records visited by eviction EvictRecordsInRange only skips Invalid/Tombstoned, not Sealed
CAS failure = no decrement OnDispose(CASFailed/InsertAbandoned) does not subtract (record was never tracked)
Elided/freelist = full cleanup OnDispose(Elided/RevivificationFreeList) subtracts remaining heap (tombstone-aware)
CopyUpdated balanced Source −value via OnDispose(CopyUpdated), destination +value after PostCopyUpdater
Delete = +key only Tombstone record adds only key overflow; value heap already subtracted at delete time
Revivification = re-add Restoring tombstoned record re-adds +value (was subtracted at delete)
HasRemoveKey (IPU) Object mutated (delta captured by Tsavorite), then ExpireAndStopOnDispose(Deleted) subtracts remaining
HasRemoveKey (PCU) PostCopyUpdater returns false, so +value is NOT added. Source handled by ClearSource or eviction

Heap Tracking by Tsavorite Operation

InternalRMW:
  Mutable IPU success  → ±delta (pre/post GetValueHeapMemorySize)
  Mutable ExpireAndStop → ±delta + OnDispose(Deleted) → −remaining
  Mutable ExpireAndResume → OnDispose(Deleted) → −value
  CAS new record       → +key, +value (after PostInitialUpdater)
  CAS copy-update      → +key, +value (after PostCopyUpdater), −srcValue (OnDispose CopyUpdated)
  In-chain revivify    → +value (after PostInitialUpdater)
  ReinitializeExpired  → +value (after PostInitialUpdater)

InternalUpsert:
  Mutable IPW success  → ±delta (pre/post GetValueHeapMemorySize)
  CAS new record       → +key, +value (after PostInitialWriter)
  In-chain revivify    → +value (after PostInitialWriter)

InternalDelete:
  Mutable delete       → OnDispose(Deleted) → −value, then SetTombstone
  CAS tombstone        → +key only

EvictRecordsInRange:
  Live record          → −CalculateHeapMemorySize (key + value)
  Tombstoned record    → −KeyOverflow.HeapMemorySize (key only)

OnDispose:
  Deleted              → −GetValueHeapMemorySize (value only)
  CopyUpdated          → −GetValueHeapMemorySize (value only)
  Elided               → −CalculateHeapMemorySize (key + value, tombstone-aware)
  RevivFreeList        → −CalculateHeapMemorySize (key + value, tombstone-aware)
  CASFailed            → no-op (never tracked)
  InsertAbandoned      → no-op (never tracked)

Tests

Tsavorite — RecordLifecycleTests.cs (12 tests):

  • CopyUpdateDoesNotFireOnDisposeCopyUpdated — copy-update doesn't fire CopyUpdated dispose on source when no explicit cleanup needed
  • CopyUpdateDisposesSourceValueExactlyOnce — source value disposed exactly once after copy-update
  • DeleteFiresOnDisposeDeletedAndNoOnDisposeDiskRecord — delete fires OnDispose(Deleted), not OnDisposeDiskRecord
  • ScanInMemoryFiresOnDisposeDiskRecordOncePerRecord — in-memory scan fires DiskRecord dispose once per record
  • ScanDiskFiresOnDisposeDiskRecordOncePerRecord — disk scan fires DiskRecord dispose once per record
  • PendingReadFromDiskFiresOnDisposeDiskRecordOnce — pending read fires DiskRecord dispose once
  • PageEvictionFiresOnEvictForEveryLiveRecord — validates per-record OnEvict callback
  • CallOnFlushGatesOnFlushInvocation — CallOnFlush=false suppresses OnFlush
  • CallOnDiskReadGatesOnDiskReadInvocation — CallOnDiskRead=false suppresses OnDiskRead
  • CallOnEvictGatingSuppressesOnEvictCallback — CallOnEvict=false suppresses OnEvict
  • ReadCacheEvictionFiresOnEvictWithReadCacheSource — validates EvictionSource.ReadCache routing
  • NoValueObjectIsDisposedMoreThanOnceAcrossLifecycle — no double-dispose across full lifecycle

Garnet — CacheSizeTrackerTests.cs (4 tests):

  • RecordHeapSizeValidationTest — heap accounting stays balanced
  • SmallMainLogFineGrainedEvictionTest — eviction triggers correct size decrements
  • RemoveLastElementReturnsTrackerToZero_IPU — removing last element via IPU path returns tracker to zero
  • RemoveLastElementReturnsTrackerToZero_PCU — removing last element via PCU path returns tracker to zero

Future TODO

The only residual subtlety worth flagging (and pre-existing to this PR) is that a TryCopyToTail produces two records sharing the same IHeapObject via TryCopyFrom. If a subsequent in-place RMW on the dest mutates that shared object (growing from X to Y), CalculateHeapMemorySize at source-evict time will return the current Y, not the originally-added X — so the source's eviction under-/over-decrement scales with post-copy mutation. The old observer-iterator path reads the same field at the same time, so it has exactly the same behavior.

Copilot AI review requested due to automatic review settings April 17, 2026 03:20
@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch from 7531edc to 4311e07 Compare April 17, 2026 03:26

This comment was marked as outdated.

@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch 3 times, most recently from 7c62bf1 to 695d6ab Compare April 17, 2026 05:25
… tracking

Garnet's `CacheSizeTracker` used `LogAccessor.SubscribeEvictions` to drive a
`LogSizeTracker.OnNext` observer that, on every page eviction, allocated a
scan iterator and walked the page to sum `MemoryUtils.CalculateHeapMemorySize`
over each non-null / non-closed record. This is heavyweight for a hot path
(buffer-pool allocation, iterator bookkeeping, epoch resume/suspend, and a
virtual dispatch per page).

This PR migrates the per-page heap-size decrement onto the per-record
`IRecordTriggers.OnEvict` hook introduced in #1695, which the object
allocator already walks during `EvictRecordsInRange`. That collapses the
"scan iterator + observer + sum" path into a single per-record callback
directly on the record we would have visited anyway.

### Tsavorite changes

- Add `EvictionSource { MainLog, ReadCache }` and thread it through
  `IRecordTriggers.OnEvict`, `IStoreFunctions.OnEvict`, and
  `IAllocator.EvictRecordsInRange`. Garnet uses this to route decrements to
  the correct counter (`AddHeapSize` vs `AddReadCacheHeapSize`).
- Change `IRecordTriggers.CallOnEvict` / `IStoreFunctions.CallOnEvict` from
  a property to `CallOnEvict(EvictionSource)` so the allocator can skip the
  per-record eviction walk entirely when the application has no work on
  that side (e.g. a read-cache-only budget should not force walks of the
  main-log allocator).
- Add `AllocatorSettings.IsReadCache` and `AllocatorBase.IsReadCache`, set
  to `true` by `Tsavorite.cs` when constructing the read-cache allocator.
  This is the cleanest way to distinguish the two allocators at
  `OnPagesClosedWorker` time without relying on the `evictCallback`
  sentinel, and is used to pass the correct `EvictionSource` to `CallOnEvict`.
- `AllocatorBase.EvictPageForRecovery` routes through the per-record
  `EvictRecordsInRange` when `storeFunctions.CallOnEvict(source)` is set.
  The legacy `MemoryPageScan(observer)` path is preserved as a fallback
  for consumers that still use `SubscribeEvictions`.
- Collapse `AllocatorBase`'s constructor to accept `AllocatorSettings`
  directly instead of unpacking individual fields at each concrete
  allocator (`ObjectAllocatorImpl`, `SpanByteAllocatorImpl`,
  `TsavoriteLogAllocatorImpl`).
- Tighten `ObjectAllocatorImpl.EvictRecordsInRange` to match
  `ObjectScanIterator`'s single-page invariant: clip `stopAddress` to the
  start page, bail on `offset == 0`, and document that both callers
  (`OnPagesClosedWorker`, `EvictPageForRecovery`) hand single-page ranges.

### Garnet changes

- `GarnetRecordTriggers.CallOnEvict(EvictionSource)` returns true only for
  the sides that are actually configured (`mainLogTracker` and/or
  `readCacheTracker` non-null), avoiding pointless per-record walks on the
  untracked allocator.
- `GarnetRecordTriggers.OnEvict(ref LogRecord, EvictionSource)` computes
  `MemoryUtils.CalculateHeapMemorySize(in logRecord)` and dispatches to
  `AddHeapSize(-size)` or `AddReadCacheHeapSize(-size)` based on the
  source. This goes through the standard asserting path — the counter must
  never undershoot zero.
- `CacheSizeTracker.Initialize` replaces the two `SubscribeEvictions`
  calls with `SetLogSizeTracker` calls so the fast-path size tracking
  during `TryCopyToTail`, `TryCopyToReadCache`, and object-page growth
  (`UpdateSize`, `IncrementSize`) continues to work unchanged.

### MainStore heap-tracking fix (root cause of negative counter)

Routing the eviction decrement through the asserting `AddHeapSize` path
surfaced a pre-existing gap: `MainStore` record-creation paths never
emitted a positive heap-size bump when a record's key or value spilled to
overflow (large inline field backed by a heap-allocated byte array). The
legacy observer path masked this silently because `OnNext` did a raw
decrement with no assertion — the counter quietly went negative on every
HLL sparse→dense transition (≈-12 KB per key) and accumulated drift
elsewhere.

`MainStore` now emits balanced heap accounting at all create/update/delete
entry points that go through a typed function callback rather than the
shared `SessionFunctionsUtils` writer (which already tracks deltas):

- `RMWMethods.PostInitialUpdater`:
  `+logRecord.CalculateHeapMemorySize()` for the freshly-created record.
- `RMWMethods.PostCopyUpdater`: `+dstLogRecord.CalculateHeapMemorySize()`
  for the new record only. The source is not subtracted — the
  `TSourceLogRecord` may be an in-memory main-log record (whose heap is
  tracked in `mainLogTracker` and will leak upward by a bounded sealed-
  source amount, parity with `ObjectStore`'s `ClearSource=false` branch
  and the legacy observer path), a read-cache record (heap lives in
  `readCacheTracker`, unrelated to this write), or a pending-IO
  `DiskLogRecord` (heap never counted in any tracker). Subtracting
  unconditionally would undercount in the last two cases and drive the
  counter negative.
- `RMWMethods.InPlaceUpdater`: `GetValueHeapMemorySize()` pre/post delta
  on `Succeeded`, so value-heap changes (e.g. APPEND, SETRANGE, or any
  path that triggers `ReallocateValueOverflow` /
  `ConvertInlineToOverflow` / `ConvertOverflowToInline`) are tracked.
- `UpsertMethods.PostInitialWriter` (all three overloads):
  `+logRecord.CalculateHeapMemorySize()` for SET-style inserts that
  create a new record through the Upsert path.
- `DeleteMethods.InPlaceDeleter`:
  `-logRecord.CalculateHeapMemorySize()` before the wrapper sets
  Tombstone. After tombstone is set, `CalculateHeapMemorySize` short-
  circuits to zero and `EvictRecordsInRange` skips the record, so
  without this decrement the creation-side increments would leak for
  every DEL of an overflow record.

The `HyperLogLogPFADD_LTM` suite is the regression that first surfaced
this — HLL sparse→dense goes through CopyUpdater and allocates ≈12 KB of
overflow for the dense representation. With the fix the counter stays
balanced and the assertion `heapSize.Total >= 0` holds throughout.

### Parity

Behavior at every record state encountered during page eviction is
bit-for-bit identical to the prior `SubscribeEvictions` path:

| Record state                                     | Old path (iterator)                | New path (per-record)        | Delta |
| ------------------------------------------------ | ---------------------------------- | ---------------------------- | ----- |
| Valid, !Sealed, !Tombstone, !IsNull              | yielded → -CalculateHeapMemorySize | OnEvict → -Calculate...      | same  |
| `IsNull`                                         | skipped by iterator                | skipped by filter            | 0     |
| `SkipOnScan` (Invalid or Sealed)                 | skipped by iterator                | skipped by filter            | 0     |
| `Tombstone` (post-delete, already ValueIsInline) | yielded → 0 via `!Info.Tombstone`  | skipped by filter → 0        | 0     |

### Hot-path cost

Fast paths (SET / GET / INCR on inline-sized values) pay only a few
aggressive-inlined inline-bit checks; `GetValueHeapMemorySize` on an
inline record early-returns 0 before any tracker call, and a
`heap != 0` guard skips the `AddHeapSize` dispatch entirely. Tracker
work occurs only when a record genuinely created, resized, or freed
an overflow/object allocation — which was already a heavyweight event.

### Testing

All on net10.0 Debug:

- `HyperLogLogTests` (incl. `HyperLogLogPFADD_LTM{32,4096}`,
  `HyperLogLogTestPFMERGE_LTM_*`) ✓
- `CacheSizeTrackerTests` ✓
- `RespListTests` (incl. `ListPushPopStressTest` ×10),
  `RespHashTests`, `RespSetTests`, `RespSortedSetTests`,
  `RespEtagTests`, `RespBitmapTests`, `RespTests.Set*`, `RespTests.Del*`:
  517/517 ✓
- Clean build on both `Garnet.slnx` and `Tsavorite.slnx` (0 warnings,
  0 errors), `dotnet format --verify-no-changes` clean.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch from 695d6ab to 9e7454c Compare April 17, 2026 06:47
…yUpdater

For in-memory CopyUpdate, Tsavorite's HeapObjectBase.CacheSerializedObjectData
cloned src.ValueObject into dst.ValueObject and Garnet's PostCopyUpdater then
cloned again, overwriting the first clone. Every ObjectStore CopyUpdate was
paying for two Clone() calls and one immediate GC.

Fix by making CacheSerializedObjectData the single point of cloning for all
sources (memory and pending-IO DiskLogRecord), and stripping the redundant
clone in Garnet's PostCopyUpdater.

Tsavorite changes (IHeapObject / HeapObjectBase / InternalRMW):
* Drop the unused 'ref LogRecord srcLogRecord' parameter from
  CacheSerializedObjectData; its only uses were an identity assert and a
  'srcLogRecord.ValueObject'-as-'this' redirect.
* Add an explicit 'bool srcIsOnMemoryLog' parameter so the method can safely
  run for DiskLogRecord sources (which cannot be expressed as ref LogRecord).
  When false, perform the clone and return immediately - skipping the
  serialization state machine, which is meaningless for ephemeral disk
  sources (the (v) data is already persisted on disk from a prior flush,
  'this' is about to be disposed up the pending chain, and
  ClearSourceValueObject is ignored by InternalRMW for non-memory sources).
* In InternalRMW, drop the 'isMemoryLogRecord' guard around the call, so
  cloning is always delegated to CacheSerializedObjectData regardless of
  source kind.

Garnet changes (ObjectStore RMWMethods):
* PostCopyUpdater now reads 'dstLogRecord.ValueObject' directly - the clone
  is always performed upstream. No conditional clone path remains here.

The single surviving clone site still runs after the successful CAS,
preserving CopyUpdater's deferred-allocation-until-CAS invariant.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch from 2da959d to 1717f9b Compare April 17, 2026 15:32
badrishc and others added 9 commits April 17, 2026 10:14
…sal sites

Before: ObjectStore PostCopyUpdater conditionally emitted +new-old when
rmwInfo.ClearSourceValueObject was true, otherwise +new. This coupled PCU to
a Tsavorite-internal signal and combined two concerns (creation of (v+1)
and removal of (v)) into one branching call site.

After: mirror MainStore's pattern by splitting into two unconditional sites.
* PostCopyUpdater always emits +value.HeapMemorySize for the (v+1) creation.
  Matches PostInitialUpdater / PostInitialWriter already doing +new.heap.
* OnDisposeValueObject(DisposeReason.CopyUpdated) emits -valueObject.HeapMemorySize
  for the (v) removal. This callback fires from InternalRMW.ClearValueIfHeap
  exactly when the source is cleared eagerly (ClearSourceValueObject=true and
  isMemoryLogRecord), which is the literal 'source freed now' signal.

Checkpoint/disk paths that leave the source alive do not reach the dispose
site; their decrement is emitted later by OnEvict when the sealed source
page evicts (via CalculateHeapMemorySize, which includes ValueObject.HeapMemorySize).
Net tracker state is bit-for-bit identical to the previous conditional form,
but each site now has a single arithmetic direction and no awareness of
Tsavorite's internal ClearSourceValueObject flag.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Simplify the record-lifecycle contract for IHeapObject values:
- Remove IRecordTriggers.OnDisposeValueObject; OnDispose(ref LogRecord, reason)
  is now the single app-facing hook. Garnet's impl merges the Deleted and
  CopyUpdated branches into one heap-size decrement.
- Drop the Action<IHeapObject> disposer lambda threaded through
  ObjectIdMap.Free, LogField.ClearObjectIdAndConvertToInline,
  LogRecord.ClearValueIfHeap/ClearHeapFields/Dispose, DiskLogRecord ctors,
  PendingContext.CopyFrom, ConditionalCopyToTail, scan iterators, and
  ISourceLogRecord.ClearValueIfHeap.
- ObjectIdMap.Free(int) is now strictly slot reclamation; it never disposes.
- DiskLogRecord.Dispose() calls ValueObject?.Dispose() itself, covering all
  its owners (PendingContext, AsyncIOContext, scan iterators, cluster
  migration / replication streaming, deserialized-from-disk).
- InternalRMW CopyUpdated path routes through
  storeFunctions.OnDispose(ref srcMemLogRecord, CopyUpdated) followed by
  srcMemLogRecord.ClearValueIfHeap().
- ObjectAllocatorImpl.OnDispose(ref DiskLogRecord) becomes a no-op.
- Update DeleteDisposeTests to the new single-hook surface.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Eliminates the asymmetry where DiskLogRecord.Dispose() unconditionally called
ValueObject.Dispose() while on-log LogRecord disposal routed through the
IRecordTriggers.OnDispose trigger. All record disposal now goes through
IRecordTriggers, giving Garnet full control over whether to dispose the
value object.

- Add IRecordTriggers.OnDisposeDiskRecord(ref DiskLogRecord, DisposeReason)
  as a required interface member with explicit no-op overrides in
  DefaultRecordTriggers, SpanByteRecordTriggers, and GarnetRecordTriggers
  (avoids DIM/interface-dispatch overhead via JIT monomorphization).
- Forward through IStoreFunctions/StoreFunctions to IAllocator, renamed
  IAllocator.OnDispose(ref DiskLogRecord) -> OnDisposeDiskRecord.
  ObjectAllocatorImpl forwards to storeFunctions (was no-op);
  SpanByteAllocator stays no-op (no IHeapObject); TsavoriteLogAllocator
  throws NotImplementedException.
- Remove ValueObject?.Dispose() from DiskLogRecord.Dispose() — callers
  now fire the trigger before Dispose. Fixes latent bug in scan-iterator
  DiskLogRecord wrappers that shared ValueObject references with the
  still-alive on-log record.
- Fire the trigger at all DiskLogRecord disposal sites:
  AllocatorBase (happy-path + retry/catch), AllocatorScan.GetFromDiskAndPushToReader,
  TsavoriteThread.InternalCompletePendingRequestFromContext, and the four
  cluster migrate/replication command sites.
- Update test IRecordTriggers impls (TrackingRecordTriggers,
  ObjTrackingRecordTriggers) to satisfy the new interface member.

All 102 relevant Tsavorite tests and 472 Garnet object-store tests pass.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…pose accounting

Adds 12 tests that precisely assert when and how many times each IRecordTriggers
callback fires across the full record lifecycle. Complements the existing
DeleteDisposeTests with coverage of the new OnDisposeDiskRecord hook and the
refactored DisposeReason / EvictionSource discriminators introduced in this PR.

Trackers:
- TrackedObjectValue (subclass of TestObjectValue) counts per-instance
  IHeapObject.Dispose invocations so tests can catch double-dispose across any
  combination of on-log, scan, pending-read, and eviction paths.
- LifecycleTracker counts OnDispose/OnDisposeDiskRecord per DisposeReason,
  OnEvict per EvictionSource, plus OnFlush / OnDiskRead — with toggleable
  CallOn* flags so tests can verify gating.

Covered behaviours:
- OnDispose(CopyUpdated) fires exactly once on immutable RMW; value dispose
  count is exactly 1 when handler opts in.
- OnDispose(Deleted) fires exactly once on delete; no OnDisposeDiskRecord.
- In-memory scan fires OnDisposeDiskRecord(DeserializedFromDisk) exactly N
  times for N records and does NOT dispose shared value objects.
- Disk scan fires the same hook exactly K times and disposes exactly K values
  when opt-in, with no double-dispose.
- Pending read from disk fires exactly one OnDisposeDiskRecord, no OnDispose,
  no OnEvict.
- Page eviction fires OnEvict(MainLog) exactly (live - tombstoned) times with
  no re-firing of OnDispose(Deleted) for tombstones.
- CallOnFlush / CallOnDiskRead / per-source CallOnEvict gating fully suppress
  their respective callbacks when false.
- Read cache eviction fires OnEvict(ReadCache) and not OnEvict(MainLog).
- No value object is ever disposed more than once across an upsert → delete →
  re-upsert → evict → pending-read cycle.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The earlier refactor in eeb6a3b split ObjectStore PCU heap-size tracking into
two sites (PCU emits +new unconditionally, OnDispose(CopyUpdated) emits -old
when the source is cleared eagerly). The same split was needed in UnifiedStore,
but its PostCopyUpdater was missed.

Result: on an EXPIRE/PERSIST that went through CopyUpdate for an object record
(e.g. SADD followed by EXPIRE), UnifiedStore.PCU still emitted +new - old while
GarnetRecordTriggers.OnDispose(CopyUpdated) also emitted -old, double-decrementing
the tracked heap size. A subsequent OnDispose(Deleted) from ReinitializeExpiredRecord
then drove the counter below zero and tripped the Debug.Assert in
LogSizeTracker.IncrementSize (HeapSize.Total should be >= 0).

Fix: mirror ObjectStore — PCU emits +new.HeapMemorySize unconditionally, and the
matching -old is emitted at the removal site (OnDispose(CopyUpdated) or OnEvict
for checkpoint/disk paths).

Fixes the four CI failures surfaced on the replace-subscribe-eviction branch:
- RespTests.ReAddExpiredKey
- RespTransactionProcTests.TransactionObjectExpiryProcTest
- RespCustomCommandTests.CustomObjectCommandTest2
- RespSortedSetGeoTests.CanUseGeoSearchStoreWithDeleteKeyWhenSourceNotFound

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…cord disposal

Three fixes from independent design reviews:

1. GarnetRecordTriggers.OnDispose(Deleted): use CalculateHeapMemorySize instead
   of only ValueObject.HeapMemorySize. This ensures overflow key/value bytes on
   MainStore string records are correctly decremented on RMW expire paths
   (ExpireAndResume, ExpireAndStop) where InPlaceDeleter does not run.
   CalculateHeapMemorySize returns 0 for tombstoned records, so this is a
   natural no-op on the mutable Delete() path where MainStore.InPlaceDeleter
   already subtracted before tombstone was set.

2. Cluster migration/replication: prevent double-trigger of OnDisposeDiskRecord
   by resetting diskLogRecord to default after the normal-path dispose, and
   guarding the finally/catch block with IsSet. Previously, a non-noop trigger
   implementation could receive a callback on a default/already-disposed record.

3. IRecordTriggers.OnDisposeDiskRecord: make it a default interface method
   (no-op) instead of requiring explicit implementation. This reduces the
   implementation burden on consumers who don't need disk-record lifecycle hooks.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…heap leak

EvictRecordsInRange previously skipped all SkipOnScan records (Sealed OR
Invalid). This leaked tracked heap for sealed-but-valid source records from
mutable-region CopyUpdates and immutable-region deletes, whose overflow
key/value bytes were never decremented from the tracker.

Fix: skip only Invalid records (already disposed/elided) and Tombstoned
records (already decremented at delete site). Sealed-but-Valid records are
now visited by OnEvict, which correctly picks up their remaining heap
contribution (overflow bytes, and value objects kept alive during checkpoint).

For records where OnDispose(Deleted) already cleared the value (immutable
delete), CalculateHeapMemorySize returns only key overflow (if any) — no
double-decrement because OnDispose decremented the full amount when the
record was not yet tombstoned, and ClearHeapFields(clearKey=false) zeroed
the value slot afterward. OnEvict sees only what remains (key overflow if
present, typically 0 for inline keys).

Updated PageEvictionFiresOnEvictForEveryLiveRecord test to use bounds
assertions reflecting that sealed source records from immutable-region
deletes are now correctly visited.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…e state

Session functions (ISessionFunctions) should not be responsible for heap-size
tracking on destruction paths — that's IRecordTriggers' job. Two places were
setting Tombstone BEFORE OnDispose(Deleted) fired, causing CalculateHeapMemorySize
to return 0 and preventing the trigger from decrementing the tracked heap:

1. SessionFunctionsWrapper.InPlaceDeleter: set Tombstone+Dirty before returning
   to InternalDelete, which then called OnDispose(Deleted). Fixed by moving
   SetTombstone+SetDirtyAndModified to InternalDelete after OnDispose.

2. SessionFunctionsWrapper.InPlaceUpdater (ExpireAndStop): set Tombstone before
   returning to InternalRMW, which then called OnDispose(Deleted). Fixed by
   moving SetTombstone+SetDirtyAndModified to InternalRMW after OnDispose.

This removes the manual cacheSizeTracker decrement from MainStore.InPlaceDeleter
(it was a workaround for the wrong ordering) and makes GarnetRecordTriggers.OnDispose
the single destruction-side decrement path for all record types.

Also tightened PageEvictionFiresOnEvictForEveryLiveRecord test to use precise
counts by observing TailAddress movement to distinguish mutable vs immutable deletes.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch from c6d6dd9 to 61089a1 Compare April 18, 2026 00:32
The CopyUpdated path is a partial clear (value-object slot only, key stays on
the record). Expecting IRecordTriggers implementers to know this nuance — that
they should subtract only ValueObject.HeapMemorySize and not the full
CalculateHeapMemorySize — is error-prone.

Move the accounting entirely into Tsavorite's InternalRMW:
- Decrement logSizeTracker by ValueObject.HeapMemorySize before clearing
- Call IHeapObject.Dispose() on the freed value object
- Then ClearValueIfHeap() nulls the ObjectIdMap slot

Remove OnDispose(CopyUpdated) from the trigger call site — the trigger is no
longer involved in CopyUpdate accounting. GarnetRecordTriggers.OnDispose now
only handles DisposeReason.Deleted. The IRecordTriggers doc is updated to
reflect that CopyUpdated is handled internally.

The trigger contract is now simple:
- OnDispose(Deleted): subtract CalculateHeapMemorySize (full record heap)
- OnEvict: subtract CalculateHeapMemorySize (whatever remains at eviction)
- Creation sites (PostInitialUpdater/Writer/CopyUpdater, InPlaceUpdater):
  add the new/changed heap

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch from 957c5c4 to 89cbce5 Compare April 18, 2026 01:18
badrishc and others added 2 commits April 17, 2026 18:31
- EvictRecordsInRange: update XML doc and skip-condition comments to reflect
  that sealed records are now visited (not skipped) and InPlaceDeleter no
  longer does heap tracking
- GarnetRecordTriggers.OnDispose: simplify comment now that tombstone is
  always set AFTER OnDispose in all paths
- Remove legacy SubscribeEvictions reference from EvictRecordsInRange doc

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…w double-subtract

OnDispose(Deleted) now uses GetValueHeapMemorySize() instead of
CalculateHeapMemorySize(). This prevents double-subtracting key overflow
bytes for immutable-region deletes where:
1. OnDispose(Deleted) fires on the source (subtracts full heap including key)
2. ClearHeapFields(clearKey=false) keeps key alive for chain traversal
3. Source is sealed (not tombstoned) — OnEvict visits it later
4. CalculateHeapMemorySize returns key overflow → subtracted again

With the fix:
- OnDispose(Deleted) subtracts value-only heap (value overflow + value object)
- For mutable deletes: tombstoned → OnEvict skips → key overflow is a bounded
  phantom freed by GC when the page is freed (same as pre-IRecordTriggers)
- For immutable deletes: sealed → OnEvict visits → subtracts key overflow once
- Net: no double-decrement, bounded key-overflow phantom on mutable deletes

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch 2 times, most recently from 53389b6 to 8e8a852 Compare April 18, 2026 05:23
Tsavorite now handles ALL heap-size decrements internally via logSizeTracker:
- OnDispose(Deleted): decrements value heap before ClearHeapFields
- EvictRecordsInRange: decrements key overflow for ALL records (including
  tombstoned), decrements value heap for non-tombstoned records
- CopyUpdated: decrements value-object heap (already internalized earlier)

GarnetRecordTriggers.OnDispose and OnEvict are now no-ops for accounting.
CallOnEvict returns false. The trigger callbacks remain available for
app-level resource cleanup (e.g. IDisposable.Dispose on value objects
that hold external resources), but Garnet does not use them.

The heap-tracking contract is now cleanly split:
- Session functions: emit +value at creation sites (only the app knows
  the heap size of a newly created value)
- Tsavorite: emit -key and -value at all destruction/eviction sites
  (the record is in hand, Tsavorite can read the sizes directly)

EvictRecordsInRange is now called whenever logSizeTracker is set OR
CallOnEvict is true, ensuring internal accounting runs even when the
application opts out of the OnEvict trigger.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch from 8e8a852 to 3b96c8c Compare April 18, 2026 05:35
Key overflow was only tracked (+key) for internal TryCopyToTail/TryCopyToReadCache
copies via logSizeTracker.UpdateSize. Records created by session functions (RMW,
Upsert, Delete) never added +key, but EvictRecordsInRange subtracted -key at
eviction — causing the tracker to undercount for overflow-key records.

Fix: add logSizeTracker.IncrementSize(+key) at the CAS success site in
InternalRMW, InternalUpsert, and InternalDelete. This pairs with the -key
emitted by EvictRecordsInRange for all records (including tombstoned).

The heap-tracking responsibility is now cleanly split:
- Tsavorite: all key accounting (+key at CAS, -key at eviction) and all
  destruction-side value accounting (-value at OnDispose/eviction/CopyUpdated)
- Session functions: +value at creation sites only

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
badrishc and others added 4 commits April 18, 2026 01:32
Previously, every ISessionFunctions implementation (MainStore, ObjectStore,
UnifiedStore, VectorStore) had to manually call cacheSizeTracker.AddHeapSize
in PostInitialUpdater, PostInitialWriter, and PostCopyUpdater. This was
error-prone — VectorSessionFunctions was missing these calls entirely,
causing heap tracking to go negative on delete (server crash).

Move all creation-site +value tracking into Tsavorite's CAS success sites
and ReinitializeExpiredRecord:
- InternalRMW: +value after PostInitialUpdater and PostCopyUpdater
- InternalUpsert: +value after PostInitialWriter
- ReinitializeExpiredRecord: +value after PostInitialUpdater (IPU path)

ISF implementations now only handle ±delta for in-place updates
(InPlaceUpdater/InPlaceWriter), where only the app knows the before/after
sizes. All other heap tracking is fully internal to Tsavorite.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
GetValueHeapMemorySize() for overflow values was returning
OverflowByteArray.TotalSize (Array.Length) while CalculateHeapMemorySize()
used OverflowByteArray.HeapMemorySize (Array.Length + 24 for .NET byte
array object overhead). This 24-byte-per-record mismatch caused the heap
tracker to go negative for overflow-value records (e.g. HLL dense) because
+value at creation used TotalSize but -value at eviction used HeapMemorySize.

Fix: change GetValueHeapMemorySize() to use HeapMemorySize, matching
CalculateHeapMemorySize(). Verified all other heap sizing paths
(KeyOverflow, ValueObject, CAS sites, eviction, OnDispose, IPU delta)
already use HeapMemorySize consistently.

Fixes HyperLogLogPFADD_LTM, HyperLogLogTestPFMERGE_LTM_DenseToDense,
and HyperLogLogTestPFMERGE_LTM_SparseToDense test failures.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
GarnetRecordTriggers no longer does any heap-size accounting — all tracking
is internal to Tsavorite via logSizeTracker. Remove the cacheSizeTracker
field, constructor parameter, and all heap-accounting comments. The struct
is now a pure no-op placeholder for future app-level resource cleanup.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Change CallOnEvict from method with EvictionSource parameter to a simple
  bool property. The per-source gating is no longer needed since Tsavorite
  handles all heap accounting internally. The EvictionSource is still passed
  to OnEvict for informational purposes.
- Update IRecordTriggers doc: remove heap-accounting implementation details
  from OnDispose/OnDisposeDiskRecord/OnEvict docs — these are now Tsavorite-
  internal. The trigger API is purely for app-level resource cleanup.
- Update InternalDelete/InternalRMW/SessionFunctionsWrapper comments to
  reference internal heap accounting instead of trigger-based accounting.
- Simplify RecordLifecycleTests CallOnEvict gating test.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch from 644e0f2 to fcbd67a Compare April 18, 2026 17:40
…ia DIM

All three gate properties on IRecordTriggers now have default implementations
returning false. Implementations that don't need any trigger callbacks (like
GarnetRecordTriggers) no longer need to explicitly declare them — the empty
struct body suffices.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch from fcbd67a to 290cfb5 Compare April 18, 2026 17:44
Add a ValueIsInline bit check before and after InPlaceUpdaterWorker to
avoid the expensive GetValueHeapMemorySize call (which chases pointers
through ObjectIdMap) on the common inline-value path. Only measure heap
when the value was or became non-inline (overflow/object transition).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc changed the title Replace SubscribeEvictions with IRecordTriggers Internalize heap-size tracking into Tsavorite via IRecordTriggers Apr 18, 2026
@badrishc badrishc changed the title Internalize heap-size tracking into Tsavorite via IRecordTriggers Internalize heap-size tracking into Tsavorite Apr 18, 2026
badrishc and others added 3 commits April 18, 2026 15:06
…ecovery

Two bugs found by GPT-5.4 review:

1. In-chain revivification (TryRevivifyInChain in InternalRMW and InternalUpsert)
   revived a tombstoned record without re-adding its value heap to the tracker.
   The value was subtracted at OnDispose(Deleted) when the record was deleted,
   but never re-added when the tombstone was reused for a new value. Fix: add
   GetValueHeapMemorySize() after PostInitialUpdater/Writer in both paths.

2. Recovery page-read used CalculateHeapMemorySize (which returns 0 for tombstones)
   but eviction later subtracts key overflow for tombstoned records. Fix: for
   tombstoned records during recovery, explicitly add KeyOverflow.HeapMemorySize
   instead of relying on CalculateHeapMemorySize.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…double-subtract

Two bugs found by Goldeneye review:

1. Elided and RevivificationFreeList dispose paths cleared heap fields
   (ClearHeapFields with clearKey=true) without subtracting from the tracker.
   Eviction skips invalid records, so the heap was never decremented.
   Fix: OnDispose now subtracts CalculateHeapMemorySize for Elided and
   RevivificationFreeList reasons (with tombstone-aware key-only fallback).

2. SubscribeEvictions(LogSizeTracker) sets both onEvictionObserver AND
   logSizeTracker to the same object. OnPagesClosedWorker and
   EvictPageForRecovery then run both MemoryPageScan (observer.OnNext)
   and EvictRecordsInRange (logSizeTracker), double-subtracting.
   Fix: skip MemoryPageScan when onEvictionObserver IS logSizeTracker.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…tStore IPU

ObjectStore InPlaceUpdaterWorker's HasRemoveKey path (e.g. SPOP/LPOP/HDEL/ZREM
removing the last element) returned false with ExpireAndStop without applying
the sizeChange from Operate. The mutation had already happened in-place
(HeapMemorySize updated on the object), but the tracker never saw the negative
delta. OnDispose(Deleted) then subtracted only the post-removal empty-collection
size, leaving the pre-removal payload permanently over-counted.

Fix: apply sizeChange to cacheSizeTracker before the early return so the
tracker reflects the in-place mutation before ExpireAndStop disposes the record.

Found by Opus 4.7 review.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc force-pushed the badrishc/replace-subscribe-eviction branch from 4046140 to 285bf22 Compare April 18, 2026 23:43
badrishc and others added 2 commits April 18, 2026 17:38
…te sizeChange

Move in-place update heap delta tracking from session functions into
Tsavorite's InternalRMW and InternalUpsert. Pre/post GetValueHeapMemorySize
measurements around InPlaceUpdater and InPlaceWriter capture the delta and
route it to logSizeTracker. This includes the ExpireAndStop path where the
object is mutated before IPU returns false.

Remove the out memorySizeChange parameter from IGarnetObject.Operate and all
implementations (Hash, List, Set, SortedSet, CustomObjectBase). The size
tracking is now fully handled by Tsavorite, so Operate no longer needs to
compute or return heap deltas.

Remove cacheSizeTracker calls from MainStore RMWMethods and
SessionFunctionsUtils (TryCopyAndUpdateOverflowValue) since Tsavorite now
handles these deltas internally.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
When ReinitializeExpiredRecord runs inside InPlaceUpdater, the outer
pre/post delta tracking in InternalRMW already captures the net heap
change. ReinitializeExpiredRecord was also calling OnDispose(Deleted)
which decremented the tracker AND cleared the value via ClearHeapFields,
causing the outer pre/post to see postHeap=0 and apply a second
subtraction. This made the tracker go negative, triggering a Debug.Assert
crash in LogSizeTracker.

Fix: for the IPU path, skip the tracker decrement but keep the disposal
side-effects (trigger + ClearHeapFields). Also remove the explicit
+valueHeap after PostInitialUpdater since the outer pre/post captures
that too. The CU path is unchanged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@badrishc badrishc merged commit 0fb650f into dev Apr 19, 2026
85 of 88 checks passed
@badrishc badrishc deleted the badrishc/replace-subscribe-eviction branch April 19, 2026 06:56
@badrishc badrishc restored the badrishc/replace-subscribe-eviction branch April 19, 2026 06:57
badrishc added a commit that referenced this pull request Apr 20, 2026
Integrates 4 new dev commits:
- #1716: Fix use-after-free in GetAllocationForRetry when page is evicted
- #1712: Internalize heap-size tracking into Tsavorite (IRecordTriggers refactor)
- #1711: Fix three broken/flaky Tsavorite and Garnet tests
- #1710: Fix native linux device

Key changes from #1712 affecting bf-tree:
- IRecordDisposer replaced by IRecordTriggers with OnEvict/OnFlush/OnDispose/OnDiskRead
- GarnetRecordDisposer replaced by GarnetRecordTriggers
- OnEvict now takes EvictionSource parameter (MainLog vs ReadCache)
- Heap-size tracking internalized into Tsavorite

Resolution: merged with -X theirs, then restored bf-tree GarnetRecordTriggers
implementation (OnEvict for BfTree disposal, OnFlush for snapshot, OnDiskRead
for handle invalidation, OnDispose for delete cleanup, OnCheckpoint/OnRecovery
for checkpoint lifecycle). Updated OnEvict signature to accept EvictionSource.
Fixed unnecessary using in ReadMethods.cs.

All tests pass: 55 RangeIndex, 345 RespTests, 34 MultiDatabase.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
badrishc added a commit that referenced this pull request Apr 20, 2026
Integrates 4 new dev commits:
- #1716: Fix use-after-free in GetAllocationForRetry when page is evicted
- #1712: Internalize heap-size tracking into Tsavorite (IRecordTriggers refactor)
- #1711: Fix three broken/flaky Tsavorite and Garnet tests
- #1710: Fix native linux device

Key changes from #1712 affecting bf-tree:
- IRecordDisposer replaced by IRecordTriggers with OnEvict/OnFlush/OnDispose/OnDiskRead
- GarnetRecordDisposer replaced by GarnetRecordTriggers
- OnEvict now takes EvictionSource parameter (MainLog vs ReadCache)
- Heap-size tracking internalized into Tsavorite via logSizeTracker
- OnDisposeValueObject removed; disposal routed through OnDispose

Resolution: took dev's Tsavorite src/test wholesale, then restored bf-tree
additions: CheckpointTrigger enum, OnRecovery/OnCheckpoint/OnRecoverySnapshotRead
hooks in IRecordTriggers/IStoreFunctions/StoreFunctions, WrongType in UpsertAction,
HybridLogCheckpointSMTask and Recovery call sites. Updated GarnetRecordTriggers
OnEvict to accept EvictionSource parameter. Re-added BfTreeInterop project ref
and WRONGTYPE guard in UpsertMethods.

All tests pass: 55 RangeIndex (3 runs), 345 RespTests. Format clean.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
badrishc added a commit that referenced this pull request Apr 20, 2026
Integrates 4 dev commits (#1716, #1712, #1711, #1710).

Key change: #1712 internalized heap-size tracking into Tsavorite and
refactored IRecordDisposer → IRecordTriggers with OnEvict(EvictionSource).

Resolution:
- IRecordTriggers: take dev's version (EvictionSource enum, OnEvict with
  EvictionSource param, OnDisposeDiskRecord, removed OnDisposeValueObject),
  add bf-tree checkpoint hooks (OnRecovery, OnCheckpoint, OnRecoverySnapshotRead)
- GarnetRecordTriggers: update OnEvict to accept EvictionSource; remove
  OnDisposeValueObject and heap-tracking from OnDispose (now internal to
  Tsavorite); keep bf-tree dispatch (OnFlush, OnEvict, OnDiskRead, OnDispose,
  OnCheckpoint, OnRecovery)
- GarnetServer: keep cacheSizeTracker + rangeIndexManager constructor
- RMWMethods PostCopyUpdater: keep ClearTreeHandle for RIPROMOTE
- Fix unnecessary using in ReadMethods.cs

All tests pass: 55 RangeIndex (3 runs), 345 RespTests, 4 CacheSizeTracker.
Format clean (Garnet + Tsavorite).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
badrishc added a commit that referenced this pull request Apr 20, 2026
Integrates 4 dev commits (#1716, #1712, #1711, #1710).

Key change: #1712 internalized heap-size tracking into Tsavorite and
refactored IRecordDisposer → IRecordTriggers with OnEvict(EvictionSource).

Resolution:
- IRecordTriggers: take dev's version (EvictionSource enum, OnEvict with
  EvictionSource param, OnDisposeDiskRecord, removed OnDisposeValueObject),
  add bf-tree checkpoint hooks (OnRecovery, OnCheckpoint, OnRecoverySnapshotRead)
- GarnetRecordTriggers: update OnEvict to accept EvictionSource; remove
  OnDisposeValueObject and heap-tracking from OnDispose (now internal to
  Tsavorite); keep bf-tree dispatch (OnFlush, OnEvict, OnDiskRead, OnDispose,
  OnCheckpoint, OnRecovery)
- GarnetServer: keep cacheSizeTracker + rangeIndexManager constructor
- RMWMethods PostCopyUpdater: keep ClearTreeHandle for RIPROMOTE
- Fix unnecessary using in ReadMethods.cs

All tests pass: 55 RangeIndex (3 runs), 345 RespTests, 4 CacheSizeTracker.
Format clean (Garnet + Tsavorite).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
badrishc added a commit that referenced this pull request Apr 20, 2026
Integrates 4 dev commits (#1716, #1712, #1711, #1710).

Key change: #1712 internalized heap-size tracking into Tsavorite and
refactored IRecordDisposer → IRecordTriggers with OnEvict(EvictionSource).

Resolution:
- IRecordTriggers: take dev's version (EvictionSource enum, OnEvict with
  EvictionSource param, OnDisposeDiskRecord, removed OnDisposeValueObject),
  add bf-tree checkpoint hooks (OnRecovery, OnCheckpoint, OnRecoverySnapshotRead)
- GarnetRecordTriggers: update OnEvict to accept EvictionSource; remove
  OnDisposeValueObject and heap-tracking from OnDispose (now internal to
  Tsavorite); keep bf-tree dispatch (OnFlush, OnEvict, OnDiskRead, OnDispose,
  OnCheckpoint, OnRecovery)
- GarnetServer: keep cacheSizeTracker + rangeIndexManager constructor
- RMWMethods PostCopyUpdater: keep ClearTreeHandle for RIPROMOTE
- Fix unnecessary using in ReadMethods.cs

All tests pass: 55 RangeIndex (3 runs), 345 RespTests, 4 CacheSizeTracker.
Format clean (Garnet + Tsavorite).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants