- Issue created by @codebymikey
The current issuer fork is a bit more optimized, but the real solution is to use the Batch API.
Currently the code for flushing the logs isn't very efficient, since it loads all the entities into memory.
It should be more memory efficient, ideally using something like the Batch API to process a set of logs at a time.
Attempt to flush a kanban log of thousands will likely result in the page crashing.
Use a more efficient API like the Batch API to flush the entities.
Use the Batch API to flush the data.
Needs work
2.0
Code
The current issuer fork is a bit more optimized, but the real solution is to use the Batch API.