FileMaker Pro 11 Portal Filtering Speed for Large Record Sets

[laudmusic]

I was wondering if anyone has had a chance to test FM11's portal filtering with large databases that are hosted FM server.

I have a solution that has 500k+ songs that are categorized. I've used portal filtering in previous versions using plugins and as well as not. I've used keywords as well as song title and lyric to filter on.

Before I adopt FM11's portal filtering, I wanted to gauge my expectations. Would love to hear about anyone else's experience.

Thanks!

Michael

[comment]

I haven't tested it myself, but...

http://fmforums.com/forum/showtopic.php?tid/214642/post/355862/#355862

[David Jondreau]

Portal filtering on large records sets is terrible slow. It's useful, and bearable, when the set has been "pre-filtered" by a relationship.

When portal filtering every record that matches the relationship is "loaded" to determine if it meets the filtering criteria. All fields, excluding unstored calcs and containers, are downloaded locally.

A relationship doesn't "load" all the fields of the related TO.

Use globals to filter the relationship until you have smallish recordsets to portal filter (I'd define small as <100).

[JerrySalem]

I wonder where the actual work is done on portal filtering? Is it done on the server or is it a function of the speed of the client machine?

[David Jondreau]

Client.

Client is almost always the answer with Filemaker.

[laudmusic]

I wish FileMaker would finally push tasks like these, sorting and portal sorting, etc. onto the server, if it's being used. One of my only complaints.