Ah yes. Maybe not the code I was thinking of, but good catch nonetheless!
On 21 August 2018 at 17:28, Stephen Searles <[email protected]> wrote: > Yup, there is a blobserver like you describe here: > https://github.com/perkeep/perkeep/blob/master/pkg/blobserver/memory/mem.go > > On Tue, Aug 21, 2018 at 12:21 AM Viktor Ogeman <[email protected]> > wrote: >> >> Thanks >> >> Sent from my phone >> >> > On 21 Aug 2018, at 01:29, Mathieu Lonjaret <[email protected]> >> > wrote: >> > >> > hmm, I thought we had an implementation of a blobserver that deletes >> > older blobs when it reaches a certain size, but nope. >> > I'm almost sure I've written something somewhere in Perkeep that does >> > something like that though, but I can't find it right now. >> > >> > >> >> On 20 August 2018 at 23:27, Brad Fitzpatrick <[email protected]> wrote: >> >> You can nuke the cache directory. It's just a cache. >> >> >> >> We should probably have some automatic size management for it. File a >> >> bug? https://github.com/perkeep/perkeep/issues >> >> >> >> (Btw, we use the perkeep@ mailing list now, not camlistore@) >> >> >> >>> On Mon, Aug 20, 2018 at 1:40 PM Viktor Ogeman >> >>> <[email protected]> wrote: >> >>> >> >>> Hi again, >> >>> >> >>> I have a perkeepd server running, storing about 200Gb of data using >> >>> blobpacked. The data is mostly jpg images. The main blob storage is on a >> >>> spinning disk ("packed") but I keep all the indexes, loose blobs + cache >> >>> on >> >>> a smaller SSD. >> >>> >> >>> I notice however that the cache directory becomes prohibitly large >> >>> (64Gb of cached blobs for 200Gb of "real data"). Is this expected? If so >> >>> why >> >>> is this, are very high quality thumbnails being stored for all the >> >>> images - >> >>> or is there some other data being cached as well? >> >>> >> >>> Finally (and most importantly) - Is it safe for me to nuke the cache >> >>> directory? (while the server is running?) Or is there some other >> >>> recommended >> >>> way to decrease the cache pressure? >> >>> >> >>> Regards >> >>> >> >>> -- >> >>> You received this message because you are subscribed to the Google >> >>> Groups "Camlistore" group. >> >>> To unsubscribe from this group and stop receiving emails from it, send >> >>> an email to [email protected]. >> >>> For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups "Camlistore" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> >> an email to [email protected]. >> >> For more options, visit https://groups.google.com/d/optout. >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Perkeep" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an email to [email protected]. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Perkeep" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Camlistore" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
