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
Formats maximum count exceeded on TPC-C #3924
Comments
Current proposal: |
kyukhin
added a commit
that referenced
this issue
Jan 22, 2019
Since under heavy load with SQL queries ephemeral spaces might be extensively used it is possible to run out of tuple_formats for such spaces. This occurs because tuple_format is not immediately deleted when ephemeral space is dropped. Its removel is postponed instead and triggered only when tuple memory is exhausted. As far as there's no way to alter ephemeral space's format, let's re-use them for multiple epehemral spaces in case they're identical. Closes #3924
kyukhin
added a commit
that referenced
this issue
Jan 24, 2019
Since under heavy load with SQL queries ephemeral spaces might be extensively used it is possible to run out of tuple_formats for such spaces. This occurs because tuple_format is not immediately deleted when ephemeral space is dropped. Its removel is postponed instead and triggered only when tuple memory is exhausted. As far as there's no way to alter ephemeral space's format, let's re-use them for multiple epehemral spaces in case they're identical. Closes #3924
kyukhin
added a commit
that referenced
this issue
Jan 24, 2019
Since under heavy load with SQL queries ephemeral spaces might be extensively used it is possible to run out of tuple_formats for such spaces. This occurs because tuple_format is not immediately deleted when ephemeral space is dropped. Its removel is postponed instead and triggered only when tuple memory is exhausted. As far as there's no way to alter ephemeral space's format, let's re-use them for multiple epehemral spaces in case they're identical. Closes #3924
kyukhin
added a commit
that referenced
this issue
Jan 25, 2019
Since under heavy load with SQL queries ephemeral spaces might be extensively used it is possible to run out of tuple_formats for such spaces. This occurs because tuple_format is not immediately deleted when ephemeral space is dropped. Its removel is postponed instead and triggered only when tuple memory is exhausted. As far as there's no way to alter ephemeral space's format, let's re-use them for multiple epehemral spaces in case they're identical. Closes #3924
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tarantool version: 2.1
OS version: any
Bug description:
When massive parallel SQL queries are executed by Tarantool, there is
a possibility for tuple formats maximum count to be exceeded.
This is due to the fact, that SQL queries are eager for ephemeral spaces
(to perform JOINs) and count of such spaces which exists simultaneously
might be big.
Even more, when space is about to be deleted,
formats are freed on lazy basis, i.e. they are only freed when
corresponding tuple is freed, which in turn freed only when we're out of space.
Steps to reproduce: Run TPC-C w/ at least 64 connections.
Optional (but very desirable):
The text was updated successfully, but these errors were encountered: