Marcus Tornberg Super Contributor.
Super Contributor.
222 views

Memory calculations


Hi all.

I know this has been discussed earlier, but I have been trying to find
an answer to my question without success for a while now searching the
forums...

I am trying to figure out how many drivers can be runned at the same
server. Lets say a server has 20 GB RAM. Its running 10 drivers and JVM
is set to initial 256MB and max 512 MB. eDirectory database cache is set
to hard limit at 512 MB.

eDirectory is 64-bit so there is no 2 GB limit on memory usage. OS is
SLES 11 SP3. IDM is version 4.5.1.

Does all drivers running as engine drivers (not Remote Loaders) shares
the same JVM inside ndsd deamon and shares 256-512 MB RAM from JVM Heap
Size settings? Or does each driver get its own JVM (inside ndsd deamon)?


What happens if I run a driver as a Remote Loader on the same phsycial
server? Does this mean that the driver shim has its own JVM (outside
ndsd deamon), but any large node sets produced by rules and policies
will consume the engine (ndsd deamon) JVM memory?

I have an environment with two identical servers (20 GB RAM) and the
settings for eDirectory/JVM as previously stated. On one server I am
running 11 drivers and on the other I am running only 2 drivers. On the
server running 11 drivers (5 running as remote loaders) ndsd has a
memory consumption of 1.3 GB RES (2280m VIRT). On the server running 2
drivers (0 running as remote loaders) ndsd has a memory consumption of
1.5 GB RES (2393m VIRT). What I'm trying to understand is how many new
drivers can be added to the environment before I need to add a new
server to the driver set (all drivers should be able to run if one
server is unavaliable).

Thank you for reading my post! 😉

Best Regards
Marcus


--
marcus_jonsson
------------------------------------------------------------------------
marcus_jonsson's Profile: https://forums.netiq.com/member.php?userid=1157
View this thread: https://forums.netiq.com/showthread.php?t=53832

Labels (1)
0 Likes
1 Reply
Knowledge Partner
Knowledge Partner

Re: Memory calculations

marcus jonsson wrote:

> Does all drivers running as engine drivers (not Remote Loaders) shares
> the same JVM inside ndsd deamon and shares 256-512 MB RAM from JVM Heap
> Size settings? Or does each driver get its own JVM (inside ndsd deamon)?


They share the same JVM and heap. They don't have to take so much memory as you suggest.

>
> What happens if I run a driver as a Remote Loader on the same phsycial
> server? Does this mean that the driver shim has its own JVM (outside
> ndsd deamon), but any large node sets produced by rules and policies
> will consume the engine (ndsd deamon) JVM memory?


Yes, exactly.
The defaults have changed with IDM 4.x to be 512M for max heap per RL instance.

> I have an environment with two identical servers (20 GB RAM) and the
> settings for eDirectory/JVM as previously stated. On one server I am
> running 11 drivers and on the other I am running only 2 drivers. On the
> server running 11 drivers (5 running as remote loaders) ndsd has a
> memory consumption of 1.3 GB RES (2280m VIRT). On the server running 2
> drivers (0 running as remote loaders) ndsd has a memory consumption of
> 1.5 GB RES (2393m VIRT). What I'm trying to understand is how many new
> drivers can be added to the environment before I need to add a new
> server to the driver set (all drivers should be able to run if one
> server is unavaliable).


I would run everything possible as a remote loader and I would not blindly accept the default per-shim memory settings.
These can vary from driver to driver, 512MB max is a good average setting, can be too low for some very busy drivers and too high for others.

The advantages of running shims in their own memory space is that if one crashes or starts chewing up too much memory, it only takes down that RL, not the entire eDirectory.
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.