Memory allocation and management 6.10 vs 6.5

[PvD_SE]

Hi folks,

One of our processes always uses a lot of memory while running. This previously lead to OutOfMemory errors. To avoid these, we've done the following:

• Use OLEDB SQL for filtering collections
• Copy data from large collections in chunks rather than as a whole
• Kill XL when no longer needed
• Run Garbage Collection
• Reduced logging levels on most actions

All of the above was implemented in BP6.5.1 and fixed our memory allocation problems for this process. 

In a current new problem with the process we find it quite impossible to analyze the problem due to the reduced logging. Many actions that usually are logged, such as decision stages, notes, start and end stages, and therefore could tell us more of what is going on are no longer logged on this process. But all of that was in good old BP6.5.4.

Since we now are running 6.10.5 one could wonder if a running BP process still has the same amount of memory available or that this has increased. If the amount of memory available to a running process would be larger and/or better managed by BP6.10.5, we could return the process to regular logging to enhance the possibilities of analyzing its logs.

Does anyone know:

• if BP6.10.5 allows for more memory to be allocated and used to a process than it did in BP6.5?
• if memory management has improved in BP6.10.5 in comparison to BP6.5?

------------------------------
Happy coding!
---------------
Paul
Sweden
------------------------------

[SimonCooke1]

Hi Paul,

I believe that the as the Blue Prism process is 32-bit then the maximum physical memory that can be allocated is 2Gb, so in terms of more memory being available this won't be the case. 

I'm not sure on any improvements on things like improved garbage collections, perhaps the version documentation goes into more detail?

Simon

------------------------------
Simon Cooke
------------------------------