3 ms·
Unsurprisingly, they benchmarked against the latest that was available at the time. It's not some nefarious trick to make the benchmarks look good. We can see t
by coder543 6y ago
Unsurprisingly, they benchmarked against the latest that was available at the time. It's not some nefarious trick to make the benchmarks look good. We can see that the heyday of OSv development work was about 7 years ago:
https://github.com/cloudius-systems/osv/graphs/contributors https://github.com/cloudius-systems/osv/graphs/contributors
Hopefully, OSv is a stable product that continues to work well, so heavy investment in development hasn't been needed on an ongoing basis, primarily just maintenance work. Or, it could be abandonware... but the README gives the impression that it is still being maintained.
I would still be hesitant to deploy such a deeply invasive solution, but the idea is interesting.
- skissane 6y ago> We can see that the heyday of OSv development work was about 7 years ago Yeah, the startup who developed this ending up pivoting to a different product instead, ScyllaDB. I think they found that while OSv is cool technology, there wasn't enough market demand to make a successful business out of it. BEA used to have a product called JRockit Virtual Edition (JRVE). It was a thin operating system designed to only run one process, the JVM. So conceptually quite similar to this, but closed source. Then Oracle bought BEA, and then after a while (not straight away after the acquisition), Oracle killed it. Rumour has it that the Linux and Solaris teams were opposed to the idea of Oracle providing a third operating system with far less features than theirs did, which is part of why it was killed. I don't think it was ever hugely popular with customers either. (Disclaimer: Used to work for Oracle, but not directly on the products mentioned.)