Guten Morgen Kollegen,
wir haben mit tideways den Fehler Session Blocking erfasst und bereits geprüft ob auf unserer Seite für den Fehler verantwortlich ist - ist aber nicht der Fall.
Um es einfacher und für Euch nachvollziehbarer zu machen, hier die Details von tideways.
Session Blocking
Estimated Impact: 81%
This trace has a Session bottleneck with 2.66 s to start a session. This can happen for two reasons:
The contents of the session are very large.
Concurrent requests to the same session id block each other.
When you make concurrent Ajax requests from the browser of a user, each of them will try to acquire a lock to the session data.
PHP prevents concurrent write access to the session data, even if you use non-file based session drivers such as Memcache.
You can unblock the sessions by calling the methodsession_write_close();. This will write the current session data to storage and all changes to the$_SESSION data afterwards are ignored/lost.
PHP Documentation: session_write_close()
Related Timeline Spans
session_start
2.66 s
wir haben mit tideways den Fehler Session Blocking erfasst und bereits geprüft ob auf unserer Seite für den Fehler verantwortlich ist - ist aber nicht der Fall.
Um es einfacher und für Euch nachvollziehbarer zu machen, hier die Details von tideways.
Session Blocking
Estimated Impact: 81%
This trace has a Session bottleneck with 2.66 s to start a session. This can happen for two reasons:
The contents of the session are very large.
Concurrent requests to the same session id block each other.
When you make concurrent Ajax requests from the browser of a user, each of them will try to acquire a lock to the session data.
PHP prevents concurrent write access to the session data, even if you use non-file based session drivers such as Memcache.
You can unblock the sessions by calling the methodsession_write_close();. This will write the current session data to storage and all changes to the$_SESSION data afterwards are ignored/lost.
PHP Documentation: session_write_close()
Related Timeline Spans
session_start
2.66 s
