FileMaker Server 21.1.4 update is now available!

Heads-Up! in the News
,
1

from the Claris Community:

Issues Addressed

1. Field definitions incorrectly read from cache

FileMaker Server 21.0 introduced an issue where field definitions were incorrectly applied to subsequent users when cached in a certain access order. Limited-access users would experience symptoms such as empty related fields, value lists, indexes, and "insufficient privileges (error -9)" when clicking into these fields. Claris has now reproduced this issue and verified that it no longer occurs in FileMaker Server 21.1.4.

2. Windows only: Server-side script sessions limited by CPU cores

FileMaker Server 21.1.3 introduced an issue where the number of simultaneous server-side script sessions could not exceed the number of CPU cores allocated to the Windows environment.

In Claris FileMaker Server 21.1.3, server-side script sessions are handled by the OS DispatchQueue. This change improves performance for CPU-bound environments by running each script session on a different CPU-thread. If all CPU-threads are busy, additional script sessions are queued up until a CPU-thread becomes available. Server-side script sessions may originate from schedules, OData, or Perform Script on Server.

The number of CPU-threads available to a system is typically 2 per CPU performance core. However on Windows, Server 21.1.3 only allocated 1 session per CPU core, leading to a performance reduction for I/O bound environments. Now in FileMaker Server 21.1.4, up to 50 server-side script sessions can be run simultaneously on Windows before queueing begins, regardless of the number of CPU cores.

If the 50 active clients do not exit properly, the system may appear stuck or hung it can due to all FMSE slots being occupied. System memory may be overloaded if an excess number of sessions become queued. To avoid these issues, it is recommended to limit the number of simultaneous clients to fewer than 50 – ideally 40 to 45 for optimal performance and reliability. Note: queueing behavior is not governed by the AllowPSoS setting.

See

3 Likes