Which Laminas SessionManager configuration avoids write-lock contention for read-only requests?

Laminas SessionManager relies on PHP's native session handler, which acquires an exclusive lock on session data from session_start() until script shutdown. Under concurrent requests sharing the same session ID, this lock serializes execution and can produce latency spikes for long-running requests.

The research indicates that SessionManager does not implement automatic early write-close, and no built-in configuration switches to read-only session access for requests that do not modify $_SESSION. While alternative storage adapters may mitigate contention, they do not remove the fundamental PHP session locking model. Runtime-dependent behavior under Swoole or RoadRunner, and PHP 7.0+ options such as session.lazy_write and read_and_close, add further uncertainty about supported patterns in current Laminas releases.

Which documented Laminas SessionManager configuration or adapter pattern allows a request to read session data without acquiring the write lock, and under what version assumptions is that behavior guaranteed? If no such configuration exists, what is the supported boundary for manually invoking session_write_close() to avoid silent data loss in clustered or high-concurrency deployments?