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 ship DL4J in a web application deployed by our users on instances of various sizes.
Also, our application uses the library minimally, the 1:1 ratio between Xmx and Dorg.bytedeco.javacpp.maxbytes is excessive.
If you don’t specify off-heap memory limit, the JVM heap limit (Xmx) will be used by default.
An instance's usage of the library depends however on the application's number of users. So, we might allocate 512MB for a 4GB instance with 5 concurrent users, but that number would have to grow linearly for an Xmx of 16GB.
Instead of us providing documentation about example scenarios to every single system administrator, we would rather be able to pass a parameter that would define which ratio of Xmx DLF4J should use across the board. For instance, 0.1.
Contributing
We are happy to work on this should the feature make sense to you.
The text was updated successfully, but these errors were encountered:
Issue Description
We ship DL4J in a web application deployed by our users on instances of various sizes.
Also, our application uses the library minimally, the 1:1 ratio between Xmx and
Dorg.bytedeco.javacpp.maxbytesis excessive.An instance's usage of the library depends however on the application's number of users. So, we might allocate 512MB for a 4GB instance with 5 concurrent users, but that number would have to grow linearly for an Xmx of 16GB.
Instead of us providing documentation about example scenarios to every single system administrator, we would rather be able to pass a parameter that would define which ratio of Xmx DLF4J should use across the board. For instance, 0.1.
Contributing
We are happy to work on this should the feature make sense to you.
The text was updated successfully, but these errors were encountered: