Skip to main content

I am beginning our journey with MVX:P and UV 11.3.4 on RHEL8.

Reading through the MVX install guide I noted that the MVAdmin installation "highly recommend"s making the following uvconfig changes
PERF_SYSTEM_SECTIONS   17
PERF_SESSION_SECTIONS   17
PERF_SYSTEM_FILES   29
PERF_SESSION_FILES  29

The default setting for these in a clean UV 11.3.4 install on RHEL8 has these set at follows:
PERF_SYSTEM_SECTIONS   17
PERF_SESSION_SECTIONS   11
PERF_SYSTEM_FILES   163
PERF_SESSION_FILES  19

The description of these settings in the uvconfig leads me to conclude that the xx_SYSTEM_xx settings are the system-wide maximums, and the xx_SESSION_xx are maximums for a monitoring session.

What I don't understand, and the documentation on MVX does not help here, is what's the relationship between the xx_SYSTEM_xx settings and the xx_SESSION_xx settings?
Are the session settings a sub-set of the system ones, or do they control something totally different to the system one?
If the session items are a sub-set of the system ones, is it safe to have them at the same settings?



------------------------------
Gregor Scott
Software Architect
Pentana Solutions Pty Ltd
Mount Waverley VIC AU
------------------------------

I am beginning our journey with MVX:P and UV 11.3.4 on RHEL8.

Reading through the MVX install guide I noted that the MVAdmin installation "highly recommend"s making the following uvconfig changes
PERF_SYSTEM_SECTIONS   17
PERF_SESSION_SECTIONS   17
PERF_SYSTEM_FILES   29
PERF_SESSION_FILES  29

The default setting for these in a clean UV 11.3.4 install on RHEL8 has these set at follows:
PERF_SYSTEM_SECTIONS   17
PERF_SESSION_SECTIONS   11
PERF_SYSTEM_FILES   163
PERF_SESSION_FILES  19

The description of these settings in the uvconfig leads me to conclude that the xx_SYSTEM_xx settings are the system-wide maximums, and the xx_SESSION_xx are maximums for a monitoring session.

What I don't understand, and the documentation on MVX does not help here, is what's the relationship between the xx_SYSTEM_xx settings and the xx_SESSION_xx settings?
Are the session settings a sub-set of the system ones, or do they control something totally different to the system one?
If the session items are a sub-set of the system ones, is it safe to have them at the same settings?



------------------------------
Gregor Scott
Software Architect
Pentana Solutions Pty Ltd
Mount Waverley VIC AU
------------------------------
Of course I got the UV version in the title wrong!

There is no way to edit it, either :(

------------------------------
Gregor Scott
Software Architect
Pentana Solutions Pty Ltd
Mount Waverley VIC AU
------------------------------

I am beginning our journey with MVX:P and UV 11.3.4 on RHEL8.

Reading through the MVX install guide I noted that the MVAdmin installation "highly recommend"s making the following uvconfig changes
PERF_SYSTEM_SECTIONS   17
PERF_SESSION_SECTIONS   17
PERF_SYSTEM_FILES   29
PERF_SESSION_FILES  29

The default setting for these in a clean UV 11.3.4 install on RHEL8 has these set at follows:
PERF_SYSTEM_SECTIONS   17
PERF_SESSION_SECTIONS   11
PERF_SYSTEM_FILES   163
PERF_SESSION_FILES  19

The description of these settings in the uvconfig leads me to conclude that the xx_SYSTEM_xx settings are the system-wide maximums, and the xx_SESSION_xx are maximums for a monitoring session.

What I don't understand, and the documentation on MVX does not help here, is what's the relationship between the xx_SYSTEM_xx settings and the xx_SESSION_xx settings?
Are the session settings a sub-set of the system ones, or do they control something totally different to the system one?
If the session items are a sub-set of the system ones, is it safe to have them at the same settings?



------------------------------
Gregor Scott
Software Architect
Pentana Solutions Pty Ltd
Mount Waverley VIC AU
------------------------------
From one of the server engineers:

  1. We recommend customer to modify xx_SYSTEM_xx and xx_SESSION_xx settings in uvconfig file. UniVerse 11.3.4 has bug in calculating performance shared memory size so we need both xx_SYSTEM_xx and xx_SESSION_xx settings same.
  2. xx_SYSTEM_xx is used to calculate total shared memory require for system wide file statistics for all UniVerse  processes.
  3. xx_SESSION_xx is used to calculate total shared memory require for process wide file statistics for each UniVerse process.
  4. PERF_SYSTEM_SECTIONS * PERF_SYSTEM_FILES = Maximum system wide files can be monitored.
  5. PERF_SESSION_SECTIONS * PERF_SESSION_FILES = Maximum process wide files can be monitored.
  6. Shared memory used to monitor files is hashed table for better performance.


------------------------------
Stuart MacKenzie
Rocket Software Inc
CO US
------------------------------
From one of the server engineers:

  1. We recommend customer to modify xx_SYSTEM_xx and xx_SESSION_xx settings in uvconfig file. UniVerse 11.3.4 has bug in calculating performance shared memory size so we need both xx_SYSTEM_xx and xx_SESSION_xx settings same.
  2. xx_SYSTEM_xx is used to calculate total shared memory require for system wide file statistics for all UniVerse  processes.
  3. xx_SESSION_xx is used to calculate total shared memory require for process wide file statistics for each UniVerse process.
  4. PERF_SYSTEM_SECTIONS * PERF_SYSTEM_FILES = Maximum system wide files can be monitored.
  5. PERF_SESSION_SECTIONS * PERF_SESSION_FILES = Maximum process wide files can be monitored.
  6. Shared memory used to monitor files is hashed table for better performance.


------------------------------
Stuart MacKenzie
Rocket Software Inc
CO US
------------------------------
Thanks for the details @Stuart MacKenzie - that helps clarify the settings for me.

The install guide mentioned setting them the same but provided no context for why.​

------------------------------
Gregor Scott
Software Architect
Pentana Solutions Pty Ltd
Mount Waverley VIC AU
------------------------------