Optimizing Portal Performance

Beginner

Measure and improve portal loading times by tuning relationship predicates, indexing, row limits, sort orders, and layout object counts.

What you'll learn

How to measure portal load time with FM Pro's performance tools
How to set effective row limits without breaking user experience
How sort fields and sort direction affect portal performance
The impact of related field count per portal row

Slow portals are one of the most common performance complaints in FileMaker. The causes are usually identifiable and fixable: too many rows loaded at once, sorts on unindexed fields, deep relationship chains, or portals with related field references that require additional hops. A systematic approach -- measure first, then fix -- prevents over-engineering and targets the real bottleneck.

1/4

Measuring portal load with the performance monitor

In FileMaker Pro Advanced, open Tools -> Debugging Controls -> Enable Script Debugger, then use the Data Viewer to watch relationship evaluation timing. For server-side performance, FM Server logs can show slow query execution times.

TEXT

// Measurement approach:
// 1. Open a layout with the slow portal on a fresh FM Pro session (clear caches)
// 2. Note the time before and after navigating to the layout
// 3. In Data Viewer: add a watch for the portal's TO::PrimaryKey
//    -- observe how long it takes to show a count
// 4. Compare with and without portal sort enabled
// 5. Compare a layout with the portal vs. without (to isolate portal cost)

// Server-side: FileMaker Admin Console -> Stats -> Query times
// Slow queries > 500ms are worth investigating

Relationship-Based Security Enterprise Data Modeling in FileMaker -- Relationship Design