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

How to reduce JVM instances to reduce memory usage for high concurrency scenario? #10

Open
wangshisan opened this issue Nov 7, 2022 · 1 comment

Comments

@wangshisan
Copy link

PG would fork a new process for each connection. So If I understand correctly, it would launch a new JVM instance for each connection in JDBC_FDW. I am concerned about the memory usage in high concurrency scenarios. Do you have any suggestion?

@khieuvm
Copy link

khieuvm commented May 17, 2023

Hello @wangshisan,

Each connection (1 application) in JDBC_FDW will create a new JVM and work on it.
And this JVM can not be shared between multi-applications: https://en.wikipedia.org/wiki/Application_Isolation_API.

By the way, if JVM can be shared between multi-applications, it is so hard to manage it. Example below:

Application 1 created a new JVM
Application 2 uses JVM's App1
Application 3 uses JVM's App1

If Application 1 crashed or ended by user and Application 2, 3 is running --> Application 2, 3??

So could you give me your opinion about 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