It is not entirely clear what resource is required if one does not plan to deploy FM Webdirect. There really is very little middle ground, so when you look at the server statistics and watch the graph crawling along the floor - thinking that you are not really using its full capacity - you may in fact be deluding yourself, as we will illustrate.Īn understanding of what server hardware resource is required to ensure that a specific number of users receive a consistently good service is clearly essential but such information is - surprisingly - a little hard to come by.įMI themselves suggest that Server – if you wish to use FM WebDirect – requires a separate CPU core - effectively a separate CPU - to handle each pair of concurrent remote calls efficiently in a smaller deployment and then gradually fewer cores as the server power and user numbers increase. fig1 – user numbers increase until Server chokes – suddenly and dramatically – with little warning. The Deskspace server performance test shown in fig 1 illustrates a common scenario as the number of users increases and suddenly performance declines – dramatically. However, Server is a binary product, in the sense that it either performs “good” or it performs “bad” - very slowly, but very reliably - as it grinds through its backlog until its load has reduced sufficiently for it to catch up on its queued calls and return to “good” mode. Why this is importantįileMaker Server 13 is a wonderful and very reliable product, provided (as with any product) you recognise, understand and work within its limits.
Summary: we will describe, discuss and illustrate the statistics that enable you to understand the why and how of FileMaker Server performance and suggest means of delivering a predictable and acceptable performance to your users. Editor’s Note: Today I am pleased and honored to present the first in what I hope will become a series of articles by guest author Nick Lightbody of Deskspace Systems Ltd.
0 kommentar(er)
