Optimizing WebDirect Performance
IntermediateLayout design and server configuration techniques that make WebDirect solutions faster for users.
What you'll learn
- How WebDirect renders layouts and what makes it slow
- Layout design techniques for WebDirect performance
- Minimizing the number of server round trips per user action
- Server hardware requirements for WebDirect at scale
WebDirect performance depends on two things: how much work the server does to render each user interaction, and how much data is transferred over the network. Both are controllable through layout design choices and server configuration. A well-optimized WebDirect layout can feel nearly as fast as FileMaker Pro; a poorly designed one will frustrate users.
The rendering model
Every time a user navigates to a new record or layout, WebDirect renders the entire layout on the server and sends the HTML to the browser. Fields with complex unstored calculations, lookups across multiple related tables, and summary fields all require evaluation time. Layouts with hundreds of objects render more slowly than simple ones.
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo