-
Notifications
You must be signed in to change notification settings - Fork 39
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
Query extremely slow when fetching many rows #61
Comments
Thanks, this and #60 gave me enough reason to turn off result prefetching. This means that we can't reliably use Connector/C until the fix hits the repos, which may take a while. Please open a new issue if problems persist. |
- Test almost all test cases of the DBI specification. - Queries not supported by the prepared statement protocol can now be run via `dbExecute()` or `dbSendStatement()`, the function `mariadbExecQuery()` has been removed (#28). - Avoid storing all results on the client due to instability with large datasets (#60, #61).
I test with the |
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary. |
DB Server: MySQL Server 5.7-15 on Fedora 24
Client: RMariaDB built against
libmariadb-client-lgpl-dev
on Ubuntu 16.04.3When I query a table of more than 8M rows and 23 columns,
dbReadTable()
will hang forever, but querying withlimit 100
will return in milliseconds orlimit 100000
in 4 seconds whilelimit 1000000
in 400 seconds. To query the whole table, it will cost a ridiculous amount of time. But withv0.11-5
and formerRMySQL
, querying this very table will only cost less than a minute.Following are tests of query the same table with different
limit
using each recent versions:devtools::install_github("rstats-db/[email protected]")
:devtools::install_github("rstats-db/[email protected]")
:devtools::install_github("rstats-db/[email protected]")
:devtools::install_github("rstats-db/[email protected]")
:The text was updated successfully, but these errors were encountered: