In TIBCO LogLogic Log Management Intelligence (LMI) version 6.2.0 and above a new feature was introduced which allows the system to dynamically allocate various resources to engines and allows users to change these settings from one place to better manage their allocations. For more information on how these allocations work or their purpose refer to article 000035598.
Although, in most cases users are able to make a guess as to what profile is applied to their LMI instance, there are situations that can cause one profile to be opted by LMI over the other. For example, if a system has resources close enough to 256G memory but is not beyond 256 or even equal to 256G, what profile is applied? To answer this question, it is dependent on the CPU cores as well as memory. But in general LMI will choose lower boundary profile rather than an upper boundary profile. This means that the system that has 220G memory will fall under 128 G category rather than 256G profile category. 

To verify this information users can cat the following file:

/var/log/pre_logappd_log

This file should contain an output similar to this:

2019-12-12 11:59:18 -    INFO: Profile: Tier 32gb_Xcores, path /loglogic/conf/vm_profiles/32gb_Xcores will be applied
2019-12-12 12:06:55 -    INFO: apply dynamic profile
2019-12-12 12:06:55 -    INFO: Profile: Tier 32gb_Xcores, path /loglogic/conf/vm_profiles/32gb_Xcores will be applied
2020-01-23 23:22:13 -    INFO: apply dynamic profile
2020-01-23 23:22:13 -    INFO: Profile: Tier 32gb_Xcores, path /loglogic/conf/vm_profiles/32gb_Xcores will be applied
2020-07-07 17:54:17 -    INFO: apply dynamic profile
2020-07-07 17:54:17 -    INFO: Profile: Tier 32gb_Xcores, path /loglogic/conf/vm_profiles/32gb_Xcores will be applied

In this case the VM has 32G memory and hence the profile selected is 32gb_Xcores. In other cases it can show output like:

2020-03-15 00:06:09 -    INFO: apply dynamic profile
2020-03-15 00:06:09 -    INFO: Profile: Tier 128gb_Xcores, path /loglogic/conf/vm_profiles/128gb_Xcores will be applied

In this case VM has 247G memory. Unless the system has 256 and above memory allocations, the profile for that size is not applied in order to protect the resource allocations for certain operations and nodes to not overextend. Users can use this output to determine the correct profile and edit only the relevant configuration files. 

This article explains how to check which phy profile or vm profile was applied to a system which can help determine the correct profile files to edit and tune.