So, this setting should not be kept at very low values indefinitely. And of course the log files will grow in size much more quickly as well. The client and top call statistics do create additional overhead for the server, so if you are already dealing with a stressed server, there is potential for further performance degradation. You can experiment with making the collection interval shorter, but only set it to very short durations (like 1 second) while diagnosing. If a previous “-old” file already existed, it will be deleted. When the file size is exceeded, the existing log file is renamed by appending “-old” to the file name, and a new log file is created. The log file size setting pertains to all of the log files, but the collection interval duration is only relevant to the three statistics log files: usage, client, and top calls. The default values are 30 seconds for the collection interval and 40 MB for the log file. In addition to enabling and disabling the log, the admin console Database Server > Logging area is used to specify the duration of the collection interval and the size of the log file. fmsadmin disable topcallstats -u admin -p pword.fmsadmin enable topcallstats -u admin -p pword.Use the command line to enable/disable top call statistics However, if the Database Server is stopped, the top call statistics log will not automatically re-enable once the Database Server is started up again.įigure 2. Once enabled, it will continue to capture information even if the admin console is closed. The top call statistics log is enabled in the admin console in the Database Server > Logging area as shown in Figure 1. * According to my understanding, the Client Statistics log is supposed to have only one entry per client for every collection interval, but in my testing, I have sometimes seen more than one entry for a client. Up to 25 entries showing discrete (not summarized) statistics from the most expensive remote calls. One entry for every client which summarizes information about the remote calls to and from that client * One entry which summarizes information about all of the remote calls, across all files and clients. Information Show for Each Collection Interval Here are the three statistics log files: Log At the end of every interval, the new information is added to the bottom of the log. Each entry in a statistics log file must be viewed from the context of its collection interval. The information stored in the three statistics log files is gathered during a collection interval whose default value is 30 seconds. Using this log file, we now have a chance at pinpointing specific operations which may be causing degraded performance. With the top call stats log, we now gain an additional tool which allows us to view statistics for individual remote calls – the top 25 most expensive ones collected during a specified time interval. Before FileMaker 15, we had a view into remote call activity only at an aggregate level, through the usage and client statistics log files. When a solution’s performance is suboptimal, it could be due to a specific action that a user (or a group of users) is taking. When we talk about “clients”, it is important to realize that this includes server-side scripts, the web publishing engine, and ODBC/JDBC connections in addition to the Pro, Go, and WebDirect clients. An example of this is when FileMaker Server asks the client for the values of its global fields. While the large majority of remote calls are initiated by the client, it is possible for FileMaker Server to initiate a remote call to the client. Some examples include navigating to a layout, creating a new record, committing a record, and performing a find. But most actions will result in one or more remote calls which are processed by the server. An example is sorting data that has already been downloaded to the client. Some of the actions that a user takes when working with a file hosted on FileMaker Server are processed entirely client-side. My motivation is to create a text-based reference, because I find that to be a more useful reference than a video.
The information here is essentially the same as in the video. I created a video on this topic back in May and am following up now with a written blog. longest elapsed time) remote calls that occur during a collection interval. With the release of version 15 in May 2016, FileMaker Server introduced a new feature – the Top Call Statistics Log – which tracks up to 25 of the most expensive (i.e.
0 kommentar(er)
