famekeron.blogg.se

1. #Filemaker pro and filemaker server fms development full#
2. #Filemaker pro and filemaker server fms development code#
3. #Filemaker pro and filemaker server fms development series#
4. #Filemaker pro and filemaker server fms development download#
5. #Filemaker pro and filemaker server fms development windows#

That is a great deal of horse-power – but we should note that FMI have reduced their recommended cores per user to about half of what they advised just a few months ago.Īnd that’s a “remote call”, not a “remote user”. fig2 – FMI Recommended Hardware Configurations for Server inc FileMaker WebDirect It is not entirely clear what resource is required if one does not plan to deploy FM Webdirect.

#Filemaker pro and filemaker server fms development full#

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.

#Filemaker pro and filemaker server fms development series#

For that reason you will want to probably purge the file of log entries after a specific project to avoid taking up unnecessary disk space.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.

Log imports can easily cause the file size to balloon to several hundred MB and can take a very long time, as the indexes are being created. Keep in mind that this file should be used locally or a LAN based FMS.

#Filemaker pro and filemaker server fms development code#

#Filemaker pro and filemaker server fms development windows#

Once you locate and open the appropriate log files in the Console app (or Windows equivalent), you might be looking at something like this:įmLogViewer will help you isolate an event across multiple log files. tech support is asking you to send them your log files. Sometimes, you need to go back beyond 15 days to find what you’re looking for.

While handy, raw log files can be difficult to read and hard to find good information.

#Filemaker pro and filemaker server fms development download#

You can download raw log files from the FileMaker Admin console interface. With the exception of Recover.log and Import.log, which are saved to the local machine, log files are found on the server. Import.log (FileMaker Pro) – Results from a schema copy / paste (or import) operation.Recover.log (FileMaker Pro) – Results from a file recovery performed by FileMaker Pro.wpe.log (FileMaker Server) – Contains events related to the Web Publishing Engine.Access.log (FileMaker Server) – Contains all connections and disconnections from clients.Event.log (FileMaker Server) – Contains file open / close events, script errors, scheduled server script run times, etc.Below is a partial list, and contains the ones most commonly used: We created a tool called fmLogViewer that makes it easier to search and find events in FileMaker Server log files. FileMaker Server produces several log files and FileMaker Pro generates at least a couple as well.