Major Performance Issues

[Layton Duncan]

I'm having major performance problems with Filemaker Server 8v2 serving to both FM7 and FM8 clients, on a particular layout.

The layout which this effects is relatively basic. It contains three fields, (a Record ID, and 2 text descriptions). It also contains two portals, one with 5 text fields. the other with 8 text fields. There are no calculations fields at all on the layout.

When there are only one or two clients connected to the server, finds on this layout runs fine. However during the day when there are 20 or so users connected to the server, moving between records takes 20+ seconds from one to the next.

The keys for the portal relationships are both just plain text fields, one has index settings of "Minimal" with "Automatically create indexes as needed" turned off, as this field is used exclusively for the relation, and not used for searching. The other is set to "All" with "Automatically create indexes as needed" turned on, as it is used in various finds.

FM Server is running on a xServe G5 with 3 gig of RAM, I can see the CPU usage jump to 80% for the filemaker process, with 20+ users connected. With a couple users, it doesn't jump this high.

As an aside, it works very fast under IWP, even during the day with all users connected.

Network speed is not an issue. Gigabit all around, (around 44MB/sec throughput during normal use). Client machines are iMac G5's.

Any tips on how to track down the cause of this dramatic slow down?

Thanks,

Layton

[Søren Dyhr]

Layouts with scrollbars? Summary/aggregate function fields on layout? Fancy graphics not using native vectorization?

--sd

[Layton Duncan]

Nope, no summaries fields.

But I have since tracked the source of the problem. It was a value list use in one of the fields in the portal. It was generated by a convoluted relationship. I simplified the relation, and now it works perfectly.

Layton

[Søren Dyhr]

Blast it! I forgot...

It was a value list use in one of the fields in the portal.

--sd