CODEWITHSUNDEEP
phpmysqlsymfony
develth
develth

Reputation: 792

symfony 3.4 FirewallListener Slow / Blocking

When i´m doing a request to a "huge" page with a lot of data to load, and make a second request to a "normal" content page, the normal page is blocked until the "huge" is loaded.

I activated the Profiler and recognized that the FirewallListener was the blocking element).

Profiler Screenshots (Loaded huge, switched tab - loaded normal) Huge Huge Page Load

Normal Normal Page Load

While the "huge" page was loaded, i did a mysql php request on cli with some time measurements:

Connection took 9.9890232086182 ms
Query took 3.3938884735107 ms

So that is not blocking.

Any ideas on how to solve that?

Setup:

Upvotes: 1

Views: 1824

Answers (3)

johanv
johanv

Reputation: 1042

We had a similar problem. When sending a couple of consecutive requests to the server in a short period, the server became very slow. I enabled the profiler bar, and a lot of time was spent by the ContextListener screenshot of the profiler information

The problem was that file server access on our server is very slow, and session information was stored on the file system, as is the default for symfony.

I configured my app to use the PdoSessionHandler, and the problem was gone.

Upvotes: 1

albert
albert

Reputation: 4468

It is been blocked by the PHP Session.

You can't serve to pages that requires access to the same session id.

Although once you close/serve/release the session on the slow page, another page can be served on the same session. On the slow page just call Session::save() as soon as possible on your controller. This will release the session. Take into consideration that everything you do after saving the session will not be stored in the session.

Upvotes: 5

Łukasz D. Tulikowski
Łukasz D. Tulikowski

Reputation: 1495

The reason the firewall takes so long is that of debug is enabled.

In debug, the listeners are all wrapped with debugging listeners. All the information in the Firewall is being profiled and logged.

Try to run the same request with Symfony debug disabled.

Upvotes: 1

Related Questions