We have recently started having performance trouble with our Filemaker
Server, and I'm having trouble coming up with a solution. I was hoping
someone here could point me in the right direction.

Symptoms include FMP6 becoming unresponsive on client computers for
10-20 seconds while switching records, performing finds, and selecting
drop-down lists.

FMS is installed on a VM running Windows Server 2003. 2.53GHz, 2.42GB
RAM, ample disk space.

FMS usage report after 2 hours of uptime:

(current,average,peak)
Cache hit% = 100,100,100
Cache Unsaved% = 0,0,1
Disk KB/sec=0,0,125
Files=62,62,62
Guests=15,15,18
Network KB/sec=0,0,123
Transactions=0,0,539

I do not understand what all these values imply. A whitepaper
published by FileMaker a few years ago suggested adjusting the cache
size down in order to keep the cache hit below 96%. I decreased the
value from 40 to 35, then to 30 all without measurable effect.

The server performs multiple functions -- file sharing, printer
sharing, and terminal server. However, we've had this configuration
for years, and only recently have had problems. There are no server
changes that correlate with decreased performance.

I'm not 100% sure that this is a FMS problem. However, pages/sec,
writes/sec, and other relevant permon counters all seem within normal
ranges.

Does anyone have any advice about how to track down this problem?

Thanks.

"Joseph O'Brien" <obrien1984 (AT) hotmail (DOT) com> a écrit dans le message de
news:ff011cec-523e-41b0-8e1f-998298b65b81 (AT) p3g2000vbv (DOT) googlegroups.com...
The first thing that should be checked is whether other copies of any of the
application files exist on other computers on the network than the server (I
know it's tedious...).
Because if it is yes, then FM may spend a lot of time figuring which is the
good one and even choose the wrong one.
Other suggestion would be to simply reinstall FMS, as it gives no harm to
the application, and as it takes 10mn.
Third thing I think of would be to switch off all worstations but one and
see if the symptoms remain. If they don't, try with the next one, etc.
Perharps, there is one which causes the difficulties encountered. If so, if
you have isolated the wrong W/S, then reinstall its local FileMaker and
maybe its link to the server, as it may be sufficient.
Please keep us posted.
Remi-Noel