Does filemaker server takes any time for creation of topcallstats.log file after the collection interval is over ?
Is true than what is the time?
the time taken to interact with the log file is slightly connected to your collection interval. If you set it to 1s, you're overdoing it anyway.
Every n seconds the server will write to the log the top 25 most expensive events occurred in these n seconds, it takes practically no time to do it. Although doing it every second might be perceived by users.
But what you are trying to intercept are long operations, stuff that takes let's say more than 10 seconds.
If you set the capture interval to 1 second, you will have the 10 second event 10 times in the log, if you set it to 10 seconds it will be there only once. What you're after is the Total elapsed seconds anyway.
My advice is to set the size of the logfile to as many MB as users you have, with a 20 sec. interval to start with, and go after the big problems.
Then you can adopt a method (many possibilities) that isolates the first and 25th record of every batch, and look at these 2 extremes, drawing conclusions.
gobimano wrote: Does filemaker server takes any time for creation of topcallstats.log file after the collection interval is over ?Is true than what is the time?
The time depends on what siplus mentioned by and large but also on the spec of your server. If your server is marginal in its performance specs then the impact of monitoring it will be higher.
The Top Call Stats log turns itself off by default when you restart FMS, that's because the FMI engineers want to minimize the impact and have you turn it on as an explicit decision each time.
Retrieving data ...