-
Notifications
You must be signed in to change notification settings - Fork 99
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
Asynchronous connections to HANA Database #153
Comments
The hana-client driver will only spawn a limited number of threads at once. This limit is governed by the UV_THREADPOOL_SIZE environment variable (the default is 4). Can you try increasing this value and see if it fixes the issue? |
Hello IanMcCurdy, thank you for response. I've already increased this parameter for my oracle connections, in that case helped. Currently it's set to 64. However in case of HANA that doesn't change anything. |
I did an experiment using your code with varying numbers of concurrent connections. With UV_THREADPOOL_SIZE set to 32 I got the following results:
Then, with UV_THREADPOOL_SIZE set to 64 I got the following:
This seems to make sense to me, the average connection time stays stable as the number of concurrent connections increases until the number of connections surpasses the number of available threads. Can you repeat this experiment and let me know what you find? |
Hello IanMcCurdy, thanks for answer. With UV_THREADPOOL_SIZE set to 32 - Connections | Average Connection time4 | 713ms UV_THREADPOOL_SIZE set to 64 Connections | Average Connection time4 | 701ms Doesn't looks that good like yours.
|
Any ideas? Can you share your code that you used? |
Refreshing, I would really appreciate any kind of support. |
Are you able to share your code for that test? Also u used node-hdb library of latest hana-client from SAP? |
hi hapvlz We're experiencing the similar performance issue with concurrent connections. Have you found a solution for the problem? Changing UV_THREADPOOL_SIZE doesn't seem to help from my testing neither. Regards |
Hello everyone,
Yes, I've seen that this project is actually closed as node-hdb has been moved under SAP development and it's under @sap/hana-client, however I would like to ask here for assistance since I do not see any possible support from SAP about it.
My target is to create simple NodeJS HANA Availability monitoring, it already works fine but not as I would expect it to work, together with new databases in monitoring the connection is taking longer and longer time.
I am running async database connections to check it availability, and then disconnect.
My code runs asynchronous but the problem seems to be in the hana library itself, as with every additional connection, the time needed to perform connections is way longer.
My code is:
Above code runs asynchronously, when I enable trace I can see that hdb.connect is being executed in parallel in the same second. But the connection is taking longer and longer with each added connection. It looks like some parameter or something that limit maximum connections in parallel - i am not sure.
Are you able to advise? Thank you in advance.
The text was updated successfully, but these errors were encountered: