Mostyn Bramley-Moore

IIUC bb-storage will only make regular/uncompressed data requests, so any communication with bazel-remote would not be compressed. If bazel-remote was using the (default) compressed storage mode then bazel-remote would need...

Hi, if you're using docker I think the easiest thing to do is tell docker to map host ports to container ports (and leave the internal ports used by bazel-remote...

I'm not a docker expert, but I think you always need to expose ports with the `-p` flag, so there doesn't seem to be much benefit in changing the internal...

> We already have two build systems (autoconf and CMake) and I believe [@evelikov](https://github.com/evelikov) is also interested in adding yet another. If we are to end up with N build...

FWIW I am considering a change to the zstd wrapper in https://github.com/mostynb/go-grpc-compression/pull/34

Hi, could you explain the use case a bit? IIUC github action caches store directories. If that's true you could potentially use that as a regular "disk" cache with bazel-remote,...

Feel free to open a PR so I can take a look. I am not sure if it will be accepted, but it sounds interesting at least :)

Sorry it took so long to get to this. I refactored your test a bit and then implemented a simpler fix which doesn't touch casblob: https://github.com/buchgr/bazel-remote/pull/826

@ulrfa encountered this limit a while back, and IIRC in that case increasing this limit only helped briefly because of the amount of disk IO backlog and the size of...

> I agree that increasing the number of threads is not suitable for addressing this issue. > > We've been running #696 in production since 2023, and it has proven...