locke4

I can reproduce this issue also. I'm working on a branch this weekend which I'm hoping will be a short-term fix. Only saw the issue when I was running some...

> @locke4 this isn't going to be anything to do with gunicorn, it's the background workers which are far more complex to replace. Fair enough, you're talking about the [Django...

As expected, doesn't fix the excessive memory usage during a delete operation. I was however able to complete the delete task (though the web browser timed out, the container didn't...

@meeb, I want to take a look at this task thing again this weekend. Am I right in thinking your desired replacement is for tasks to be offloaded to a...

I've got a couple of thoughts that'd I'd appreciate your thoughts on @meeb after my prototyping my feature branch on this issue yesterday. 1. I've created celery tasks for all...

> Thanks for the effort, @locke4! Specifically for your questions: > > 1. Ideally, `background_tasks` needs to be completely removed. This is blocking upgrading Django beyond 3.2 as well as...

This is a fantastic library by the way, I too found plotters and plotly weren't as useful as this library. I'm testing it out with WASM and Yew. One suggestion...