As Silk Performer is a 32 bit application, there is a limitation to the amount of memory that can be committed for specific actions to be carried out (similar to all 32 bit processes). One such action is the merging of load test result files into one "m@...tsd" file. After a load test has completed, remote agent files (i@ files) are zipped and transferred to the controller. In normal circumstances, on the controller, these i@ files are merged to present one m@ file (merged result data). If these i@ files are large, for example 200MB to 1GB (and above), given the limitation in terms of memory that can be used to complete the process, the merge action may fail (no m@ file is generated). The next logical step if the automatic merge process fails would be to use ‘Custom Merge Wizard’ in Silk Performance Explorer to manually merge the files. If a number of large files are used in this custom merge process, then a possible result will be a “TSD: 14- Memory allocation failed. The system maybe out of memory” error displayed within the Silk Performance Explorer output window. Unfortunately, due to the memory restrictions, Silk Performance Explorer will be unable to merge the files. This limitation has been recognized and a new process to allow larger result files to be merged within Silk Performance Explorer is scheduled to be included within Silk Performer 16.5. The workarounds currently available reduce the amount of data included in the files. These workarounds include: 1. Increasing the ‘Computational Interval’ to a value higher than the default – 10 seconds and running the load test again – SILK PERFORMER | SETTINGS | ACTIVE PROFILE | RESULTS | TIME SERIES. Keep in mind that the shorter the interval and the longer the load test, the more data will be generated. 2. Removing unnecessary timers / web forms within the script. During a recording in Silk Performer, a request may be made to an application add-on of some sort, facebook, google etc that will result in unneeded requests within the BDL script. These requests will likely contain timers / web forms that will add additional overhead to the result files. In this instance the best sequence of actions to take would be to carry out a new recording but suppress the calls to the specific domain in question. Further information on suppressing calls can be found within the Silk Performer online help – SILK PERFORMER | FILE | CONTENTS.
↧