Re: Best database for implementing a cache
- From: Arne Vajhøj <arne@xxxxxxxxxx>
- Date: Fri, 30 Mar 2007 21:11:11 -0400
vj wrote:
Why not just write then to the disk directly? Most File Systems can be
treated as a form a database, and it seems like thats kind of what you
want anyway.
Yes i am writing the image files directly to the filesystem as it is.
However i need to limit the size of the cache so that it may not grow
arbitarily large. that would require me to maintain access count
metric for evicting existing stored images. Since filesystem itself
would not let me assiciate this info with the image I tought of a
utilizing a database that would store the access count as well as all
the available images in the cache.
What about keeping files on disk, having meta data in memory and
simply rebuilding meta data at startup (list all files on disk
and start with zero counters) ?
Arne
.
- Follow-Ups:
- References:
- Best database for implementing a cache
- From: vj
- Re: Best database for implementing a cache
- From: Daniel Pitts
- Re: Best database for implementing a cache
- From: vj
- Best database for implementing a cache
- Prev by Date: Re: What sort of documentation is most useful for a java application?
- Next by Date: Re: latest best practice
- Previous by thread: Re: Best database for implementing a cache
- Next by thread: Re: Best database for implementing a cache
- Index(es):
Relevant Pages
|
|