Jump to content

slowness in filemaker 5 server


This topic is 8586 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies

There is a general problem of slowness with server 5 for macintosh. We have 45 table (complete accounting program) working with filemaker 3 and also with filemaker 5 in two different network with 10 customers in each one.

There is a ramdom behavior of slowness in filemaker 5 server. Sometimes this behavior have a precise cause and sometimes we don

Link to comment
Share on other sites

First, FMS will indeed run fastest if it is the front app. It does not like being relegated to a background app.

Two, the more memory you allocate to FMS can be a two edge sword. The good thing is the amount of info you can hold in cache. The down side is the amount of data that can potentially need to be flush to disk.

So, I'm bettin' you have your cache flush set to execute when the machine is idle. That's sort of true, it executes when machine is idle or when the cache is full, and when the flush happens you will take a performance hit. Conceivably with depending on hardware bottlenecks, and enough transactions happening during a cache flush you could extend the performance hit almost indefinitely.

Solution, set you disk flush to happen at timed intervals. This way you are not letting a lot of data store in RAM.

HTH

Link to comment
Share on other sites

Check you are using the latest patch level of FileMaker Pro Server (and MacOS for that matter). Also be sure that the *clients* are all using the latest versions of FMP.

Link to comment
Share on other sites

This topic is 8586 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.