Skip to content
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

poor performance of resultSetIterator.rows.next() #190

Open
andrejs-sisojevs opened this issue Sep 28, 2018 · 1 comment
Open

poor performance of resultSetIterator.rows.next() #190

andrejs-sisojevs opened this issue Sep 28, 2018 · 1 comment

Comments

@andrejs-sisojevs
Copy link

We did a stress test to our module:

  • query 10k rows
  • each row containing 20 columns
  • each row with size of 8.5KB
  • expect query to download results within 20 seconds

Module based on node-jdbc downloaded results in 80 seconds. Profiling showed resultSetIterator.rows.next() to work slowly (resultSetIterator is obtained by calling resultSet.toObjectIter()).

We had to abandon node-jdbc and rewrite DB client part of system in Java, and call it using nodejs subprocess spawn. It now performs fine.

@theterra
Copy link

@andrejs-sisojevs-accenture Can you share an example code. how you resolved it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants