Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Oh, fun, they finally published this. How many times I've had to catch myself from saying the word "Borg" I don't even know.

The performance isolation is good, but I wouldn't really seek after high utilization unless compute costs are significant to your business. We've seen some crazy things where nominally non-interfering jobs cause significant performance degradation to other jobs on the same node. There's work yet to do here.



Why is everyone acting like the name was some big secret? Everyone who has been using Mesos knows Borg, for crying out loud, big writeups were published in Wired and The Verge over 2 years ago!


Whether I'm allowed to speak about a project's codename has little to do with whether it has been leaked through nonofficial channels.


It was a secret. You weren't allowed to mention borg outside Google. Note John Wilkes was generally careful about not saying the name was 'Borg' or acknowledging it as such and instead referred to 'Omega'.


Perhaps you were told it was secret. It was not secret. Here's one of the articles I was referring to. http://www.wired.com/2013/03/google-borg-twitter-mesos/ John Wilkes mentions Borg, acts coy about the name for some reason (seems like a pattern), and mentions Omega, its nascent replacement.


John does not mention Borg by name publicly (well, until the paper was published). That's what I meant (consistent with what I was replying to). The article you linked to confirms that.

"According to Wilkes, Google plans to publish a research paper on Borg (though he still won’t use the name). "

Wilkes won’t even call it Borg. “I prefer to call it the system that will not be named,"

(I work with John and have contributed to Borg)


Perhaps you two are using different definitions of the word "secret". You are probably using the word to mean "a fact that no one outside of a select group of people knows". dekhn is probably using it to mean "a fact which my company has said we are not allowed to publicly acknowledge".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: