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

[Filippo_Nicolussi_P]

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. 

[hugo_andrade]

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]

@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

[tduarte]

@Filippo_Nicolussi_P @Sonja_Bauernfeind 
We have the following recurrent error on all our nodes (System Repository):
"API call to Engine service was not successful: Failed to get app 'StaticByteSize'."

We are on May 2025 Patch2.
Is there a fix for this or is the recommendation still to disable the Base memory size ?
What is the practical impact of these errors on the system?

[tduarte]

@Filippo_Nicolussi_P @Sonja_Bauernfeind any updates on the above?

[AkashPohare_HB]

Hello @Filippo_Nicolussi_P , @Sonja_Bauernfeind , we are also having same error message in the Trace _ Sysytem_repository log. This issue started only after upgrade to May 2025 Patch 4 version from May 2024 Patch 4. Any fix available for this issue?

[Sonja_Bauernfeind]

Hello @AkashPohare_HB 

If you are experiencing similar issues on other versions, please log a support ticket so we can take a closer look.

All the best,
Sonja 

[tduarte]

I contacted Qlik Support a few weeks ago and instructions are to either follow this article or wait for the November 2025 release.

[Filippo_Nicolussi_P]

Hi. 

November 2025 was released two days ago, and other patches for others version mentioned in article above were also released. 

Finding the messages in the logs with "StaticByteSize", doesn't mean you must disable the functionality, you could, in case you have also the node overloading RAM and CPU by Repository and Engine. 

Please check at today the Download Site providing to update to the latest supported patch/version accordingly to your current version.  

Once updated/upgraded if you have previously disabled the functionality as per article enable it back, node by node monitor Repository Engine overload as described above. 

In case of doubts on your issue, or a not perfect much with above, after updating/upgrading to a supported version/patch before disabling the functionality just for the messages in the logs reported, open a support ticket. 

[tduarte]

Hi @Filippo_Nicolussi_P 

I don't see any reference to this subject in the latest May 2025 patch https://community.qlik.com/t5/Release-Notes/Sense-Enterprise-on-Windows-release-notes-May-2025-Initi... or November 2025 https://community.qlik.com/t5/Release-Notes/Sense-Enterprise-on-Windows-Release-Notes-November-2025-...

Can you please confirm in which versions/patches this was made available?

Thanks,
Telmo

[Filippo_Nicolussi_P]

Hi @tduarte  

Exact, not all tickets reaching R&D are defect and reported in the release notes. 

For the one mentioned above: 

QB-22795 related to internal user updating the "Memory Size" into the database, correction is present all today supported version and patches, should also be in above list on point "1. Verify you ..." . 

QB-24301 was a customer context investigation that documented, as above reported, the ability to selectively disable the two aspects of that functionality.

Hope this clarifies your doubts.