Tristan Pierquet Posted October 9, 2020 Share Posted October 9, 2020 Hello all, We are currently facing problems with one of our deployments ; its memory consumption goes up and up until the engine finally ends with an OutOfMemoryException. The engine recovers, except for the job that caused the Exception. We identified that the problem was because of the presence of various variables during the lifetime of the job that could be initialized with a large amount of data. The Memory Saving Mode is currently disabled (default value). Is there any reason for this option to be disabled dy default Are there any drawbacks to enable this mode on our engine This particular engine does not use any Shared Variable, but makes frequent requests on our DataBase. Thanks for your answers. Regards, Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now