-
Notifications
You must be signed in to change notification settings - Fork 8
feat(analytics): expose write/read transaction queue depth (count) metrics #1689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kriszyp
wants to merge
2
commits into
main
Choose a base branch
from
kris/txn-queue-depth-metrics-592
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| require('../testUtils'); | ||
| const assert = require('assert'); | ||
| const { setupTestDBPath } = require('../testUtils'); | ||
| const { table } = require('#src/resources/databases'); | ||
| const { setMainIsWorker } = require('#js/server/threads/manageThreads'); | ||
| const { transaction } = require('#src/resources/transaction'); | ||
| const { getTransactionQueueDepths } = require('#src/resources/DatabaseTransaction'); | ||
| // The queue-depth accounting lives on the base DatabaseTransaction (RocksDB path). LMDB writes/reads | ||
| // route through the separate LMDBTransaction overrides (resources/LMDBTransaction.ts), which maintain | ||
| // their own unrelated trackedTxns set and do not feed this accounting — matching the existing | ||
| // RocksDB-only carve-outs in transaction.test.js. | ||
| const isLMDB = process.env.HARPER_STORAGE_ENGINE === 'lmdb'; | ||
|
|
||
| describe('Transaction queue depth metrics', () => { | ||
| let QueueTest; | ||
|
|
||
| before(function () { | ||
| setupTestDBPath(); | ||
| setMainIsWorker(true); | ||
| QueueTest = table({ | ||
| table: 'QueueDepthTest', | ||
| database: 'test', | ||
| attributes: [{ name: 'id', isPrimaryKey: true }, { name: 'name' }], | ||
| }); | ||
| }); | ||
|
|
||
| it('returns the expected shape and resets high-water marks on read', function () { | ||
| const depths = getTransactionQueueDepths(); | ||
| for (const key of ['writeDepth', 'writeMaxDepth', 'readDepth', 'readMaxDepth']) { | ||
| assert.equal(typeof depths[key], 'number', `${key} should be a number`); | ||
| assert.ok(depths[key] >= 0, `${key} should be non-negative`); | ||
| } | ||
| // After reading, the high-water marks are reset to the current instantaneous depth, so an | ||
| // immediate second read (with no intervening activity) reports maxDepth === depth. | ||
| const after = getTransactionQueueDepths(); | ||
| assert.equal(after.writeMaxDepth, after.writeDepth); | ||
| assert.equal(after.readMaxDepth, after.readDepth); | ||
| }); | ||
|
|
||
| it('records a committed write on the write-queue high-water mark, then drains to zero', async function () { | ||
| if (isLMDB) return; | ||
| getTransactionQueueDepths(); // reset the sampling window | ||
| await QueueTest.put(1, { name: 'first' }); | ||
| const depths = getTransactionQueueDepths(); | ||
| // The commit resolved before put() returned, so the instantaneous depth is back to zero, but the | ||
| // high-water mark captured the in-flight commit. | ||
| assert.ok(depths.writeMaxDepth >= 1, `writeMaxDepth should have captured the commit, got ${depths.writeMaxDepth}`); | ||
| assert.equal(depths.writeDepth, 0, 'write depth should drain to zero after the commit settles'); | ||
| }); | ||
|
|
||
| it('reflects an open read transaction in the read-queue depth', async function () { | ||
| if (isLMDB) return; | ||
| getTransactionQueueDepths(); // reset the sampling window | ||
| await QueueTest.put(2, { name: 'second' }); | ||
| let observedReadDepth = 0; | ||
| await transaction({}, async (context) => { | ||
| // A read inside the transaction opens a tracked read snapshot. | ||
| await QueueTest.get(2, context); | ||
| observedReadDepth = getTransactionQueueDepths().readDepth; | ||
| }); | ||
| assert.ok(observedReadDepth >= 1, `an open read transaction should be counted, got ${observedReadDepth}`); | ||
| }); | ||
| }); |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.