Quoting Brad Fitzpatrick (2019-05-07 01:23:13) > diskpacked is good for write throughput, but not great for reads (often > bad locality). blobpacked (the default) has perfect locality for files > and has fast paths that cut through a bunch of the layering for > sequential reads (e.g. downloading a file that is otherwise in > thousands of logical blobs), but does more work on uploads. When your > data grows slowly over time, that makes sense. When you're mass > importing data into it, it's not very ideal.
Thanks for the explanation, this makes sense. -Ian -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/perkeep/155723930894.824.8984699950972324424%40localhost.localdomain. For more options, visit https://groups.google.com/d/optout.
