Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Writing results temporarly to memory #16

Closed
psychok7 opened this issue Apr 6, 2017 · 0 comments
Closed

Writing results temporarly to memory #16

psychok7 opened this issue Apr 6, 2017 · 0 comments

Comments

@psychok7
Copy link

psychok7 commented Apr 6, 2017

Would you consider a new feature (if there is not a similar one already that i couldn't find) which is writing the celery results in a temporary cache backend (like Redis for example), and having a callable Django management command to retrieve multiple results and dump them in bulk as well into a Database (Postgres for e.g)??

This way we could have the "historical" data without massacring our database even if it was not up to date.

In my case i only check these results in Django admin once in a while and before i do, i see myself running the command (or assigning it to celery beat) to get the updates into the database and into the admin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant