Ekb keeps everything in ram

[DavidLeoni]

The ODR Entity Knowledge Base (Ekb) holds imported and modified entities, concepts, etypes. It is not a real db, they're just Java data structures that currently holds everything in ram, and this is a problem especially for entitities (both created and imported). In the long run after many imports memory will eventually get saturated. We should have a real db that keeps in ram stuff and when it overflows it flushes to disk.

[gbella]

Why cannot you flush the EKB after the end of each project?
For aborted projects this is admittedly not possible but that's another problem that could be solved, e.g., by flushing stuff that gets stale (for example, after 1 month).
These are workarounds but would they not work in practice?

[DavidLeoni]

We can try to do as you suggest, it might work, but this stuff will require testing and bugfixing so we need to decide for which version of odr it will be implemented. For the 0.3.6 I think it's quite late...

[gbella]

I agree. Let's leave it for later.