We are using HDB_NODEJS_THREADPOOL_SIZE attribute to increase worker threads in pool as per the recommendation for one of our nodeJS CAP module. Internally we use sap-cds to get a transaction and run the db queries against hana cloud.
It helped us run the DB queries against HC parallelly.
A year back, I tested this in my laptop and it was working for me in one of our nodeJS(CAP) module.
Recently I found the attribute has no effect and same I verified in my laptop.
Initially I though may be some new OS upgrade is blocking this.
As HDB_NODEJS_THREADPOOL_SIZE overrides UV_THREADPOOL_SIZE, I tested libuv’s non-blocking IO feature by utilizing UV_THREADPOOL_SIZE attribute with the help of a sample nodejs program and it worked(not with CAP).
Want to understand if any change at CAP side blocking this?
Request clarification before answering.
Hi,
There have been no recent changes to the Node.js driver's usage of the HDB_NODEJS_THREADPOOL_SIZE environment variable and we have just confirmed that it works as expected in the latest version of the driver. Perhaps this environment variable is getting cleared before it reaches the Node.js driver by some intermediary layer.
Mike
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My point was that although I don't know what's happening in the CAP layer, our team's testing for the Node.js driver itself shows the HDB_NODEJS_THREADPOOL_SIZE environment variable working as expected.
I notice that you've opened an internal support ticket for this issue. I believe this will be helpful in determining why your queries seem to be executing sequentially.
One thing that might help is turning on API call tracing in the Node.js driver to observe if the Node.js driver is being called concurrently or sequentially:
hdbsqldbc_cons trace filename nodejs-%p.txt
hdbsqldbc_cons TRACE API ON LEVEL DEBUG
Mike
Hi,
Perhaps check this:
The new HDB_NODEJS_THREADPOOL_SIZE environment variable specifies the number of worker threads in the thread pool. The formerly used UV_THREADPOOL_SIZE environment variable is still respected, but is overridden by HDB_NODEJS_THREADPOOL_SIZE. If neither is set, a default value of 4 worker threads is used.
Kind Regards,
Johan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.