search

anukat2015 / elda

Automatically exported from code.google.com/p/elda
0 stars 0 forks source link

Elda caching needs investigation / adjustment / documentation #60

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
* it's not clear how much benefit the cache brings in a multi-client context.

* the drop-all nature of the cache may provoke load peaks. Integrating an
  LRU policy should be investigated.

* we don't have good numbers for how much room cache entries take. That makes
  it hard to size the cache (or the application memory).

* view cache units, currently APIResultSets, may be too big. We should consider
  caching at eg the Resource x View level. May not be useful if too many (small)
  queries generated instead.

Original issue reported on code.google.com by ehog.he...@googlemail.com on 20 Jul 2011 at 12:40

GoogleCodeExporter commented 8 years ago 
This list doesn't capture the notion from a previous issue, that the Elda cache 
should not take up more memory than is available, i.e. should not get out of 
heap space errors when there is data in the cache.  Ref:  weak references

Original comment by br...@epimorphics.com on 25 Jul 2011 at 8:22