This is based on the idea that if the server isn't performant being able to support more users - who are going nowhere - is meaningless. Is there some condition that I didn’t know where the test will stop after a certain amount of time and/or specific conditions?" Correct, the test is designed to automatically curtail when the server ceases to be performant, which I have set as the average completion time for each task exceeding, from memory, 3 seconds. We tested this way with up to 15 users to obtain our figure of 32mb RAM being used per WD user session (on OS X) "When I set it for 100 intense users with 6 tokens, it got up to 43 users, then stopped. This means you need to work hard to keep all the user sessions active so they don't close. The server is set to 500 (max) script sessions and licensed for up to 101 WD users." Are you opening a series of browsers / browser tabs on your local machine(s) and calling dsBenchmark from each? To simulate WD sessions you must create one browser window or tab for each user. "Strangely, with a WebDirect connection, the most users it’ll go up to is 3 although I selected 10 to test with. You will realise that ds Benchmark is open to the community so you can see exactly how this is done, and no doubt improve on it, if you care to. The Dequeue line shows the amount of delay being introduced by the Token mechanism. This is predicated on our view, based on about 4 months of research, that ultimately more is done in the time if the task queue is slowed and the server encouraged to retreat from moving towards choking. With Tokens set to 1 or more the solution monitors the current speed of each task completion, amongst all the virtual client server side scripts, and adds a delay before the next call is made, in order to reduce the pressure on server. How it affects the testing?" We have written here about the possible use of Tokens, programmed into the Filemaker solution, to improve the load management of FileMaker Server under "What is tokenisation and can it help performance?" With Tokens set at 0 tokenisation does not operate. There is more information about dsBenchmark here "What is the dequeue (red line) for,Ĭan you explain what the Token setting is for and In recent versions of FMS you need to user terminal to do this with: fmsadmin set serverconfig scriptsessions=500 In earlier versions the limit number can be set in the Ui. To run dsBenchmark you should set this limit to 500. This limit can be set to any value up to a maximum of 500. The default setup for FileMaker Server limits those Perform Script on Server sessions to 25. Are you familiar with this issue and how might I test these machines to their limits? Thank you." Yes, dsBenchmark uses the creation of server side sessions to simulate multiple users by means of calling Perform Script on Server WITHOUT telling the calling script, a loop, to pause until the called script has concluded. Both machines are running the same 25 user license (site lic.). I suspect that the FileMaker script engine connections are somehow limited on each machine. The number of connections just flatlined. It both cases I watched my server stats from the server admin dashboard and nothing seemed to be too heavily taxed. In the first instance the test topped out at 100 connections and on the second instance at 25. More… Pausing Scripts Executed by FileMaker Server 11 or Previous.DsBenchmark: FAQs Here are some questions we have answered about dsBenchmark "I just ran dsBenchmark on a colocated Mac mini and on a machine with a FM hosting company. But what do you do when you need to pause a script being executed by FileMaker Server when you are using an earlier version of FileMaker? In other words, export, pause, and then import.įor FileMaker 12, you can simply use the Pause/Resume Script step because it is compatible with FileMaker Server. The answer, if you can’t tell where I’m heading, is to place a pause between these two script steps. As a result, the script would either throw an error or simply not complete the process as expected. I found, for example, that if I created a server-side script which contained an export/import process, there were times that the script didn’t seem to wait for the export to complete before trying to import from the file created by the previous step. Over the years, I’ve had to deal with the need to slow down a script being run by FileMaker Server many times and thought I’d write about how I do it. The solution was to pause the script in question. I came across a blog post recently which focused on an issue where a script, run from FileMaker Server, kept failing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |