You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are finding some general performance issues with thick mode. We understand thin mode is developed to address most of them. But many of our client environments are forced to stay with thick mode. Please work towards reducing these thick mode performance issues.
In general, we note two observations
As we move to higher version from (5.5.0) api response times increase. (i.e throughput decreases).
Memory consumption is comparatively too high.
Performance summary by version
We have tabulated throughput tests from version 5.5.0 to the latest 6.8.0.
Version
Total Throughput (req/sec)
Create (req/sec)
FindById (req/sec)
Update (req/sec)
Delete (req/sec)
5.5.0
1184.36
403.60
403.93
296.46
297.01
6.7.0
1142.23
387.82
387.45
286.22
286.67
6.7.1
1047.45
349.34
349.14
262.15
262.25
6.8.0
954.48
326.61
326.16
239.01
239.28
PFA the sample expressjs app which is used for performance testing along with jmeter script and instructions on how to run. app.zip
Comparative RSS memory performance
We have compared rss memory performance with postgres javascript client. While it is not a fair comparison, the difference is significant. This is captured in the pdf file attached. The jmeter file shared earlier can be tweaked and a test loop has to be authored. The loop would perform a test load (or bust); for e..g with a concurrency of 10 and 1000 requests. Followed by an idle period of 10 min. The test loop can be repeated for sufficient number of times or for a duration of more than 2 hours. This is how the graphs were composed.
We are finding some general performance issues with thick mode. We understand thin mode is developed to address most of them. But many of our client environments are forced to stay with thick mode. Please work towards reducing these thick mode performance issues.
In general, we note two observations
Performance summary by version
We have tabulated throughput tests from version 5.5.0 to the latest 6.8.0.
PFA the sample expressjs app which is used for performance testing along with jmeter script and instructions on how to run. app.zip
Comparative RSS memory performance
We have compared rss memory performance with postgres javascript client. While it is not a fair comparison, the difference is significant. This is captured in the pdf file attached. The jmeter file shared earlier can be tweaked and a test loop has to be authored. The loop would perform a test load (or bust); for e..g with a concurrency of 10 and 1000 requests. Followed by an idle period of 10 min. The test loop can be repeated for sufficient number of times or for a duration of more than 2 hours. This is how the graphs were composed.
Memory consumption comparison 1.pdf
PS: all these tests were done on rhel linux with instant oracle client 21.8
The text was updated successfully, but these errors were encountered: