Your question:
>Which Cognos log files should be refreshed and studied for performance tuning and affinity requests?In the past I did ipfclientconfig.xml performance analysis. This would give good insights into request hitting GW, APP and DB server, execution time in any component and the time for sending it back to the client.
In C11.1.x some components of logging have changed, so I am not shure if ipflogging is still the best way to do this.
In general from ipclient you could understand how much time is lost in GW, APP and DB as well as rendering.
Affinity is about short term request navigating the portal and triggering execution = low affintiy
And about retrieving a report from one app.-server doing it = high affinity
Tuninig this I found it very helpful to use jMeter and rampup usage of high and low affinty, filling up RAM and CPU usage.
So ... looking at just one logfile is not usefull. In the past, looking at ipfclientconfig.xml and setting up different loggings was the best approach.
------------------------------
Ralf Roeber
https://linkedin.com/in/ralf-roeber-470425a/------------------------------
Original Message:
Sent: Mon March 29, 2021 09:00 AM
From: Elihu El
Subject: Performance Tuning
Good Morning,
I hope that your day has gotten off to a good start. Which Cognos log files should be refreshed and studied for performance tuning and affinity requests?
Warm Regards,
Eli
#CognosAnalyticswithWatson