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

Introduce Redis to handle resources #68

Closed
rsarky opened this issue Jul 18, 2020 · 3 comments
Closed

Introduce Redis to handle resources #68

rsarky opened this issue Jul 18, 2020 · 3 comments

Comments

@rsarky
Copy link
Contributor

rsarky commented Jul 18, 2020

After a conversation with @rralf I realised that a lot of the problems and hacky things we do in PaStA is while trying to persist stuff. Currently we are persisting stuff in an ad-hoc way in text files and caches and trying to simulate a database.

What if we actually used a database instead? I dont have a lot of experience with Redis but seems like it could be a good fit for this usecase.

Other database options can be considered too

@rralf
Copy link
Member

rralf commented Jul 18, 2020

Indexes are not just for simulating a database. They give a human-readable overview and allow manipulation with standard tooling.

However, I agree that we can use databases for replacing the pickle-hell that we currently have. There might be another student that will evaluate this topic (hopefully soon).

@rsarky
Copy link
Contributor Author

rsarky commented Jul 19, 2020

Indexes are not just for simulating a database. They give a human-readable overview and allow manipulation with standard tooling.

A human readable overview could be a view into the database.

The choice of a database will also depend on whether the data that we need to store can fit in memory

@rralf
Copy link
Member

rralf commented Jul 19, 2020

But regarding memory consumption, indexes are not a major issue. It's the pickle files (i.e., commit caches), and the way how python duplicates memory when doing things in parallel. If we want to benefit from databases, then a persistent, non-relational in-memory database (e.g., key-value store) would probably be the best choice. So yes, redis could be a promising candidate.

@rralf rralf closed this as completed Jul 2, 2024
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