What is pgo files in qlikview?

Profile-guided optimization (PGO) lets you optimize a whole executable file, where the optimizer uses data from test runs of the .exe or .dll file. The data represents the likely performance of the program in a production environment.

Profile-guided optimizations are only available for x86, x64, or ARM64 native targets. Profile-guided optimizations aren't available for executable files that run on the common language runtime. Even if you produce an assembly with mixed native and managed code (by using the /clr compiler option), you can't use profile-guided optimization on just the native code. If you attempt to build a project with these options set in the IDE, a build error results.

To use profile-guided optimization, follow these steps to optimize your app:

It's even possible to create the optimized executable file and later determine that additional profiling would be useful to create a more optimized image. If the instrumented image and its .pgd file are available, you can do additional test runs and rebuild the optimized image with the newer .pgd file, by using the same /LTCG and /USEPROFILE linker options.

The profile-guided optimizations include these checks and improvements:

Read more about these environment variables, functions, and tools you can use in profile-guided optimizations:

Environment variables for profile-guided optimizations These variables were used to specify run-time behavior of testing scenarios. They're now deprecated and replaced by new linker options. This document shows you how to move from the environment variables to the linker options.

PgoAutoSweep A function you can add to your app to provide fine-grained .pgc file data capture control.

pgosweep A command-line utility that writes all profile data to the .pgc file, closes the .pgc file, and opens a new .pgc file.

pgomgr A command-line utility that adds profile data from one or more .pgc files to the .pgd file.

QlikView

BorrowedCalData

BorrowedCalData.pgo contains information about leased licenses (which machine it was leased to, which user and when it was leased). Unless using leased CALs, there should be very little access to this file (and it should be very small).

TicketData

TicketData.pgo contains issued tickets. When one node authenticates a client it gives it a ticket which can later be used to start a session on any of the other nodes. Those nodes then validate the ticket (by looking in TicketData.pgo) rather than doing an authentication. There are two accesses for each new session (one when the ticket is created and one when it is looked up/consumed).

IniData (all setting.ini s)

IniData.pgo contains the same information as the settings.ini for the QVS, in a different format and synced between the nodes. The nodes will regularly read from the file to see if there are changes (roughly once every 5 seconds), or write their changes if they receive some changed setting from the QMC. Since the file is so small it is usually not a performance issue to do this once every 5 seconds, especially if you only have 2 or 4 nodes.

ServerCounters

ServerCounters.pgo contains basic statistics for each node in the cluster, such as DocLoadsSinceMidnight, DocLoadFailsSinceMidnight, SessionStartsYesterday and LastUpdate timestamp to show that the node is still alive. It should be accessed once or twice per minute and contain very little information.

CalData

• Stop QlikView Services.
• Edit the QlikView Server's Settings. ini file. Locate Settings.ini C:\ProgramData\QlikTech\QlikViewServer and add the following entry under the [Settings 7] node: PgoAsXmlAlso=1.
• Start Services. Load pgo.

QlikView Server has five Persistent Global Object (PGO) files for storing server side non-application specific data.