top | item 32115865

(no title)

stickupkid | 3 years ago

Citation required on this one...

gVisor is used in a lot of places[1] that require more performance than a clock. I'm not saying you can't achieve more performance with C++/rust, what I'm saying is that this probably isn't the primary concern.

1. https://cloud.google.com/kubernetes-engine/docs/concepts/san...

discuss

order

staticassertion|3 years ago

https://gvisor.dev/docs/architecture_guide/performance/

https://gvisor.dev/docs/architecture_guide/performance/#netw...

Network performance in gvisor is awful and, by gvisor's own documentation, this is a matter of "implementation costs" ie: it is how gvisor is written, not gvisor's fundamental constructs, that makes it slow.

The rest of the benchmarks are notable as well, there are a few other places where the implementation is called out as being a problem.

saurik|3 years ago

So maybe they should team up and work on replacing gVisor with something that shares as much code as possible with this new thing, which one would hope would be architected in a way to be able to help replace gVisor?

Fnoord|3 years ago

> Citation required on this one...

You mean you'd like to read a source to back up that statement.

Nothing is required...