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

Why not saving result to Redis firstly instead of MongoDB directly? #166

Open
jkryanchou opened this issue May 11, 2017 · 2 comments
Open

Comments

@jkryanchou
Copy link

I have got insighted into your worker implementation. While I found that worker has heavily write to Mongo.
I thought it might not be a good performance on saving result. Why not writing to redis (cache) firstly to instead of saving to MongoDB in order to handle more I/O operations to gain more performance.

@sylvinus
Copy link
Contributor

sylvinus commented Mar 2, 2018

This should be possible with simple overloading of the Job class. Add it as an example/recipe ?

@jkryanchou
Copy link
Author

@sylvinus I would post it later. I mean that using cache (redis or any other cache-db) to handle concurrent reads/writes before writing to MongoDB.

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

2 participants