Skip to main content
Announcements
Qlik Connect 2025! Join us in Orlando join us for 3 days of immersive learning: REGISTER TODAY

How to disable 'Base memory size' info and 'StaticByteSize' calls in Qlik Sens Enterprise on Windows

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Filippo_Nicolussi_P

How to disable 'Base memory size' info and 'StaticByteSize' calls in Qlik Sens Enterprise on Windows

Last Update:

Feb 19, 2024 7:32:57 AM

Updated By:

Sonja_Bauernfeind

Created date:

Feb 19, 2024 3:14:13 AM

After upgrading to Qlik Sense Enterprise on Windows May 2023 (or later), the Qlik Sense Repository Service may cause CPU usage spikes on the central node. In addition, the central Engine node may show an increased average RAM consumption while a high volume of reloads is being executed. 

The Qlik Sense System_Repository log file will read:

"API call to Engine service was successful: The retrieved 'StaticByteSize' value for app 'App-GUID' is: 'Size in bytes' bytes." 

Default location of log: C:\ProgramData\Qlik\Sense\Log\Repository\Trace\[Server_Name]_System_Repository.txt

This activity is associated with the ability to see the Base memory size in the Qlik Sense Enterprise Management Console. See Show base memory size of apps in QMC.

Resolution

The feature to see Base memory size can be disabled. This may require an upgrade and will require downtime as configuration files need to be changed.

Take a backup of your environment before proceeding.
  1. Verify the version you are using and verify that you are at least on one of the versions (and patches) listed: 

    • May 2023 Patch 13
    • August 2023 Patch 10
    • November 2023 Patch 4 
    • February 2024 IR
  2. Back up the following files:

    • C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
    • C:\Program Files\Qlik\Sense\Repository\Repository.exe.config

      *where C:\Program Files can be replaced by your custom installation path.

  3. Stop the Qlik Sense Repository Service and the Qlik Sense Dispatcher Service
  4. Open and edit the capabilities.json with a text editor (using elevated permissions)
    1. Open C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
    2. Locate: "enabled": true,"flag": "QMCShowAppSize"
    3. Change this to: "enabled": false,"flag": "QMCShowAppSize"
    4. Save the file  
  5. Open and edit the repository.exe.config with a text editor (using elevated permissions)
    1. Open C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
    2. Locate: </appSettings>
    3. Before the </appSettings> closing statement, add:
      <add key="AppStaticByteSizeUpdate.Enable" value="false"/>
    4. Save
  6. Start all Qlik Sense services
  7. Verify you can access the Management Console

If any issues occur, revert the changes by restoring the backed up files and open a ticket with Support providing the changed versions of repository.exe.config, capabilities.json mentioning this article. 

Related Content

Show base memory size of apps in QMC

 

Internal Investigation:

QB-22795
QB-24301

 

Environment

Qlik Sense Enterprise on Windows   May 2023, August 2023, November 2023, February 2024. 

Labels (1)
Comments
hugo_andrade
Partner - Creator II

Hi @Filippo_Nicolussi_P ,

On a scenario with multiple servers and the Central server not being used for HUB nor Scheduled tasks, would this behavior be seen?

If this turns out to be true, the ideal scenario wouldn't be to disable the function, but to let it be populated by one of the other Engines that are serving the HUB or Scheduler services.

Thanks for sharing the steps.

rafaelbessa79
Contributor II

@Filippo_Nicolussi_P 

meu ambiente on premises está configurado com multi nós, onde nó central, engine, proxy e scheduler estão separados.

Se esse ajuste fizer sentido para meu ambiente, você indicaria fazer em qual servidor?

abraços