3 of 3 people found this helpful
I don't think there is a comprehensive guide. I've found that the most useful way to approach this is to run some tests in isolation. Put your solution on a dev server so that you can be the only one connected. Then everything in the top call log will be you.
Remember that the top call log will only record the top x calls in the given timespan. So interpreting the log for a busy production server can be difficult because it will not show the complete action of any one user, only the bits and pieces that were expensive. Which is very scattered way of collecting data and difficult to detect patterns.
You are right. Making sense of top 25 call stats of a server with 180 rather active users isn´t showing the whole picture at all. ;-) OK, so I´ll try finding out what the stats tell me by using your isolation approach... But still... If FileMaker is reading this --> It´s time for a tech brief on server stats!