Skip to content
This repository has been archived by the owner on Mar 21, 2022. It is now read-only.

Cache landscape objects #39

Open
lotzk opened this issue Jan 3, 2019 · 1 comment
Open

Cache landscape objects #39

lotzk opened this issue Jan 3, 2019 · 1 comment
Labels
enhancement on hold
Milestone
Future Release

Comments

@lotzk
Copy link
Contributor

lotzk commented Jan 3, 2019

The most recently used landscape objects should be held in a cache to avoid I/O. As mentioned in #38, landscape objects will be persisted as json-api strings, identified by unique (numeric) id. We can utilize Redis as an in-memory-cache for those string.
@Alexander-Krause-Glau Alexander-Krause-Glau added this to the Release 1.3.2 milestone Jun 11, 2019
@Alexander-Krause-Glau
Copy link
Contributor

At the moment I am experimenting with a Redis cache to see if our stringified Mongo-DB approach is really so much slower.

@Alexander-Krause-Glau Alexander-Krause-Glau removed this from the Release 1.4.1 milestone Oct 7, 2019
@czirkelbach czirkelbach added this to the Future Release milestone Dec 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement on hold
Projects
None yet
Milestone
Future Release
Development

No branches or pull requests
3 participants
@Alexander-Krause-Glau @czirkelbach @lotzk