-
Notifications
You must be signed in to change notification settings - Fork 12
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
Slow Query - no results in DDErl #541
Comments
@c-bik I tested the query and indeed we have a timeout when pressing restart which I am looking into right now. However in your example using the driver directly you are fetching only one row |
This is hardcoded in DDErl. I propose a way to optionally override it (
The way this // 4GB is the maximum size you can write stdout as we are framing with 32 bit length header
if ( rows_fetched < N && erl_rows_term_size < 4GB ) {
// fetch more rows
} else {
// reply to erlang with fetched rows
} There are no fetch timeout in current driver and packing multiple rows in one payload increases pipe throughput. However, a new idea can be |
@c-bik probably will have to implement a configurable fetch block size at the end in any case so the user can tweak it as his preference, but still I would like to find a better solution for it to work even if not optimally with the default settings. As a solution on the fsm we will buffer rows for a configurable period of time defaulting to
Will add an issue to erloci with this feature request. FYI: @stoch |
QUERY
CRASH
Query Details
ERLOCI Code
Rows can be fetched with direct erloci APIs successfully!
expand for details
FYI: @stoch
The text was updated successfully, but these errors were encountered: