search

lipinggm / tlb

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

Use weak-references for repositories(and flush em back on finalize) #54

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
As of now, when tlb-server blows the heap at some point(this happened once with 
go03 server).

Original issue reported on code.google.com by singh.janmejay on 1 Feb 2011 at 1:24

GoogleCodeExporter commented 9 years ago 
Use something like EH Cache so that we do not have to worry about clearing out 
our caches ourselves.

Original comment by itspa...@gmail.com on 17 Mar 2011 at 8:17

GoogleCodeExporter commented 9 years ago 
One way to do it is to use a better datastore, so we don't have to keep 
hard-reference based caches. Attempting move to Cassandra in a separate branch.f

Original comment by singh.janmejay on 10 May 2011 at 8:21

GoogleCodeExporter commented 9 years ago 
Cassandra seems to have high memory requirements. TLB server is supposed to be 
very light weight. Ditching cassandra spike for now. Will leave the branch 
intact (so work on it can be continued at a later point, if required). Will 
spike using Ehcache for now(leverage LRU reclamation).

Original comment by singh.janmejay on 7 Jun 2011 at 12:39

GoogleCodeExporter commented 9 years ago 
Using ehcache for this.

Original comment by singh.janmejay on 12 Jul 2011 at 3:59

GoogleCodeExporter commented 9 years ago

Original comment by singh.janmejay on 12 Jul 2011 at 3:59

GoogleCodeExporter commented 9 years ago 
Fixed in 4c6ec91bd2efb7ab54df5e5e49c4649a7cbffe39 (master)

Original comment by singh.janmejay on 15 Jul 2011 at 8:51