8000 decoding stats should lock once by onursatici · Pull Request #6587 · vortex-data/vortex · GitHub
[go: up one dir, main page]

Skip to content

decoding stats should lock once#6587

Merged
onursatici merged 1 commit intodevelopfrom
os/stat-lock
Feb 19, 2026
Merged

decoding stats should lock once#6587
onursatici merged 1 commit intodevelopfrom
os/stat-lock

Conversation

@onursatici
Copy link
Contributor

Summary

setting stats for a decoding array currently locks per stat, api supports to lock it once with set_iter

Closes: #000

Testing

Signed-off-by: Onur Satici <onur@spiraldb.com>
@onursatici onursatici added the changelog/performance A performance improvement label Feb 18, 2026
@onursatici onursatici merged commit 402b7a0 into develop Feb 19, 2026
51 of 52 checks passed
@onursatici onursatici deleted the os/stat-lock branch February 19, 2026 13:52
fastio pushed a commit to fastio/vortex that referenced this pull request Mar 10, 2026
<!--
Thank you for submitting a pull request! We appreciate your time and
effort.

Please make sure to provide enough information so that we can review
your pull
request. The Summary and Testing sections below contain guidance on what
to
include.
-->

## Summary

setting stats for a decoding array currently locks per stat, api
supports to lock it once with `set_iter`
<!--
If this PR is related to a tracked effort, please link to the relevant
issue
here (e.g., `Closes: vortex-data#123`). Otherwise, feel free to ignore / delete
this.

In this section, please:

1. Explain the rationale for this change.
2. Summarize the changes included in this PR.

A general rule of thumb is that larger PRs should have larger summaries.
If
there are a lot of changes, please help us review the code by explaining
what
was changed and why.

If there is an issue or discussion attached, there is no need to
duplicate all
the details, but clarity is always preferred over brevity.
-->

Closes: #000

<!--
## API Changes

Uncomment this section if there are any user-facing changes.

Consider whether the change affects users in one of the following ways:

1. Breaks public APIs in some way.
2. Changes the underlying behavior of one of the engine integrations.
3. Should some documentation be updated to reflect this change?

If a public API is changed in a breaking manner, make sure to add the
appropriate label. You can run `./scripts/public-api.sh` locally to see
if there
are any public API changes (and this also runs in our CI).
-->

## Testing

<!--
Please describe how this change was tested. Here are some common
categories for
testing in Vortex:

1. Verifying existing behavior is maintained.
2. Verifying new behavior and functionality works correctly.
3. Serialization compatibility (backwards and forwards) should be
maintained or
   explicitly broken.
-->

Signed-off-by: Onur Satici <onur@spiraldb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/performance A performance improvement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0