System Alert: Lumira Server Max Heap Size Check

[former_member196781]

Hello,

This is regarding the description of the "System Alert: Lumira Server Max Heap Size Check" of the BIPST.

It tells:

"The recommended MaxHeap (-Xmx) value for the Lumira APS 16gb minimum, 32gb recommended. This is due to the amount of memory required by the Lumira in-memory data engine. If any Lumira APS is found with less than 16gb set on its command line parameter, this alert will trigger."

Even if it makes sense to increase the max heap setting imo anyway, we got the info from SAP that the in-memory engine (Velocity engine) is not using heap space, but it's using native memory.

It can be limited by adding the parameter -Dhl.maximummemory=<% value> or <kb value>.
If this is not set, it can allocate up to 85% of the available free memory of the respective host machine.

Best Regards
Moritz

[former_member240871]

Thanks for the information about the parameter Moritz.

I'll follow up with the team and Lumira folks about the parameter since I can't find too much info about it right now.

Cheers,

Leslie

[former_member196781]

Hi Leslie,

Thanks for your actions.

Best Regards
Moritz

[former_member240871]

Hi Moritz,

I checked with the senior Lumira folks about the behaviour.

1. Heap Memory is used for BW-Live or HANA-Live reporting where the database does the calculations. Because it's using -Xmx to configure memory usage, it'll take up to that much memory if possible, but generally won't unless you use those two use-cases heavily. It's recommended to increase it to at least what the alert is set to and let the allocator/garbage collector figure out memory usage on the Java side if it is required.

2. -Dhl.maximummemory=<% value> or <kb value>

This was intended to be an internal parameter. While it is available for use, it won't be supported by SAP if any issues come up when it's used. There's no documentation on it anywhere, and that is intentional.

The alerts is accurate as-is, and doesn't need to change.

Regards,

Leslie