Albert Casademont

@mathieudz didn't see any memory limit crashes on our logs. Still, we should also keep an eye on it.

LGTM!

Sure! Should we slpit these changes in 2 different commits? Also, AFAIK (not 100% as i don’t use mongo), symfony should clean the entity managers automatically, those were little hacks...

@mathieudz this is one of the dangers of switching to a long running process like react-php/php-pm that manages more than one request. Developers need to be fully aware that the...

@mathieudz would be great to have a repro test-case, I'm using php-pm in a stateless REST api, so no sessions on our end to see what might be happening.

Sure, this is taken from ReactPHP's website, for example ```php $loop = React\EventLoop\Factory::create(); $server = new React\Http\Server(function (Psr\Http\Message\ServerRequestInterface $request) { //Lots of calls and work here return new React\Http\Response( 200,...

@jcchavezs yes exactly. We're right now using PHP-PM which limits concurrency for the ReactPHP loops but in theory they could be running in parallel. ReactPHP has the concept of Middlwares...

I believe some of this issues will be solved by the new Network Endpoints Group load balancing (https://cloud.google.com/kubernetes-engine/docs/how-to/container-native-load-balancing) due to the removed network hop in the kube-proxy

Hi! Is this still relevant? We're using Docker and right now mpdf is by far the fattest package due to the fonts directory. Composer's `suggest` would be the best way...

Chiming in here. We're also bugged by not being able to use `CURRENT_TIMESTAMP(6)` as a default value without getting it quoted, seems like only `CURRENT_TIMESTAMP` is allowed when doing a...