Hi guys what is the purpose of this table `spy_event_behavior_entity_change` ?

UM9F81RCP

Hi guys
what is the purpose of this table spy_event_behavior_entity_change ?

UKEP86J66

It's the cache of all events generated in a request. At the end of the request they are all fetched and pushed into the event queue. If this succeeds they are deleted.

UM9F81RCP

i see

UM9F81RCP

is there a way to disable them ?

UM9F81RCP

actually lets discuss it from another point .. is it possible that this has an impact on performance ?

Unknown

Kind of ... Responses will be sent back to the clients before executing this code (it's handled on kernel event). BUT ... the process stays alive until the events have been published into the queue. There's two problems with this:
1.) If you use session locking, the lock will only be removed when the PHP process shuts down. This leads new requests waiting to acquire a session lock resulting in slow throughput from a client perspective
2.) Since the processes keep on living after responses have been sent back, you might exhaust available FPM workers if you have lots of incoming requests. This will result in clients waiting for free resouces and eventually getting a timeout error.

Unknown

On the other hand: Sending messages to the queue should be fairly quick so the scenarios I described are rare

UM9F81RCP

thank you Thomas

Unknown

You're very welcome