Optimize large set of processed data for API calls

mogilvie / EncryptBundle

Encryption bundle

89 stars 29 forks source link

Optimize large set of processed data for API calls #20

Closed Volmarg closed 1 year ago

Volmarg commented 3 years ago

I was trying to localize the bottleneck in my API calls. That's the one

Without that:

Start: 17:57:40
End: 17:59:28
Duration: 1min 48s
Result: not even half gets transferred and each call gets slower.... and slower... had eventually timeouts

With that:

Start: 18:05:29
End: 18:06:06
Duration: 37s
Result: done, everything works

mogilvie commented 3 years ago

I'll have to test this, particularly around the impact of detaching the entity postFlush. I'm thinking where the controller goes on modify the entity again and tries to flush the subsequent changes but it will have been detached.

mogilvie commented 1 year ago

Tested detached entities, not in favour of detaching from the entity manager.

However, you can implement your own DoctrineEncryptSubscriber and reference it in the spec_shaper_encrypt.yaml under subscriber_class.