@cmuratori In that case, baked PAKs + metadata in RAM is better than a real FS filename lookup (which is likely to trigger its own IO).
@cmuratori @rygorous I'm just talking about the fact that if you want to ensure "1 physical IO per image", then that's very hard to do.
-
-
@cmuratori@rygorous In fact it may actually be impossible if you can't cap the image size, etc. -
@cmuratori@rygorous But certainly you _could_ get close to that by _actually writing a filesystem_.
End of conversation
New conversation -
-
-
@cmuratori@rygorous Paper says "the blockmaps for several contiguous large files can be small enough to be stored in main memory" -
@cmuratori@rygorous And "This benefit does not imply that Haystack can guarantee every photo read will incur exactly one disk operation." - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.