{"push_id":550222013,"size":1,"distinct_size":1,"ref":"refs/heads/metadata-index","head":"30529d2cf785a7a4e317509e347b86cfa8a1e6ba","before":"31b0457e243695550a2c2a3256b5a6b3a6f89aa1","commits":[{"sha":"30529d2cf785a7a4e317509e347b86cfa8a1e6ba","author":{"email":"3d0f3b9ddcacec30c4008c5e030e6c13a478cb4f@danner.de","name":"Daniel Danner"},"message":"Add metadata search index for more responsive FUSE\n\nThis adds the construction of a metadata index during archive creation,\nwhich can be used to narrow down the location of particular entries\nwithin the items list. The FUSE mount uses this index to fetch only\nthose chunks that are relevant to the specific operation instead of\nfetching the metadata of the entire archive.\n\nAs a result, using FUSE mounts of large archives is consirably more\nreponsive. And more importantly, the performance decrease linearly with\nthe archive size anymore. Bulk operations that require the full metadata\ntree anyways (such as running \"find\" on the entire archive) are not\nnegatively impacted.","distinct":true,"url":"https://api.github.com/repos/dnnr/attic/commits/30529d2cf785a7a4e317509e347b86cfa8a1e6ba"}]}