You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Files over ~500mb / ~1gb give mirror trouble b/c the RPC framework (grpc-java) we use for "really snappy bi-directional streaming" only supports in-memory / on-Java-heap byte[]s for its RPC messages, and doesn't support passing around zero-copy files / memory regions like netty's FileRegion.
So, for now, mirror just can't really send those sort of files unless/maybe you give it a huge heap.
We should probably detect the current size of heap, guess that we can do files ~half that size, and just ignore any file larger than that, which is basically #37.
The text was updated successfully, but these errors were encountered:
Files over ~500mb / ~1gb give mirror trouble b/c the RPC framework (grpc-java) we use for "really snappy bi-directional streaming" only supports in-memory / on-Java-heap
byte[]
s for its RPC messages, and doesn't support passing around zero-copy files / memory regions like netty's FileRegion.So, for now, mirror just can't really send those sort of files unless/maybe you give it a huge heap.
We should probably detect the current size of heap, guess that we can do files ~half that size, and just ignore any file larger than that, which is basically #37.
The text was updated successfully, but these errors were encountered: