Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Expose the underlying metrics behind the scan limits #835

Closed
scgray opened this issue Feb 26, 2020 · 0 comments
Closed

Expose the underlying metrics behind the scan limits #835

scgray opened this issue Feb 26, 2020 · 0 comments
Assignees
@scgray

Comments

@scgray
Copy link
Contributor

scgray commented Feb 26, 2020

The ExecuteState is contained within the ExecuteProperties (for better or for worse) to perform resource limiting (max records scanned and bytes scanned) and, as a natural part of this process, the limiters contained therein are tracking the number of records and bytes scanned. Users of this API should have some mechanism for, later, asking the ExecuteState (or maybe the ExecuteProperties?) for this information.
@scgray scgray self-assigned this Feb 26, 2020
scgray pushed a commit to scgray/fdb-record-layer that referenced this issue Mar 2, 2020
Resolve FoundationDB#835: Expose bytes/records scanned through Execut…
521abd3 
…eState

This includes some efforts to still allow for the use of the
`NO_LIMITS` constant in fashion that should have little overhead
on execution performance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@scgray scgray

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@scgray