You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve the performance of update by parallelising reads. Implement интернал async update method. (#2087)
#### Reference Issues/PRs
<!--Example: Fixes#1234. See also #3456.-->
Implement `async_update_impl` function which returns a future. The
synchronous version for update just calls it and waits for the future
just like append does.
This keeps most of the code for update the same, however instead of
calling `.get` on futures it will chain then and return a future. In the
process of doing this the reads needed by update were made in parallel.
Thus the regular update will have improved performance.
Slight refactor of C++ unit tests, using std::array instead of
std::vector for fixed size collections and placing const and constexpr
specifiers. No functional changes.
#### What does this implement or fix?
#### Any other comments?
#### Checklist
<details>
<summary>
Checklist for code changes...
</summary>
- [ ] Have you updated the relevant docstrings, documentation and
copyright notice?
- [ ] Is this contribution tested against [all ArcticDB's
features](../docs/mkdocs/docs/technical/contributing.md)?
- [ ] Do all exceptions introduced raise appropriate [error
messages](https://docs.arcticdb.io/error_messages/)?
- [ ] Are API changes highlighted in the PR description?
- [ ] Is the PR labelled as enhancement or bug so it appears in
autogenerated release notes?
</details>
<!--
Thanks for contributing a Pull Request to ArcticDB! Please ensure you
have taken a look at:
- ArcticDB's Code of Conduct:
https://github.com/man-group/ArcticDB/blob/master/CODE_OF_CONDUCT.md
- ArcticDB's Contribution Licensing:
https://github.com/man-group/ArcticDB/blob/master/docs/mkdocs/docs/technical/contributing.md#contribution-licensing
-->
0 commit comments