Hacker Newsnew | comments | show | ask | jobs | submit | Bjoern's comments login

More on the topic of Dancing Robots, HRP-4C from AIST & Kawada

https://www.youtube.com/watch?v=xcZJqiUrbnI

-----


Further reading:

http://rideonewheel.com/

https://www.kickstarter.com/projects/4422853/onewheel-the-se...

-----


Here is a well balanced explanation why ECC-RAM. That being said, if the RAM is the weakest link it doesn't matter what underlying FS is used.

https://pthree.org/2013/12/10/zfs-administration-appendix-c-...

In my experience 16GB is only needed if you want to run Deduplication.

-----


> "if the RAM is the weakest link it doesn't matter what underlying FS is used"

When is this ever the case, though? Even non-ECC RAM is more reliable than hard drives except when a RAM chip has died, which most ECC systems don't handle well either. Full chipkill capability is pretty rare.

-----


As I understand the reasoning, it's that ZFS checksumming creates a risk of false positives where non-checksumming filesystems wouldn't have them. So without ECC RAM you're trading the risk of losing data to your IO chain for the risk of losing data to increased RAM activity. With ECC RAM it's an unambiguous win.

-----


It sounds to me like there must be some situation where ZFS reads data from disk, verifies the checksum, keeps it in memory where it could get corrupted, then recomputes the checksum on the corrupted version and writes either the corrupted data or the incorrect checksum to disk but not both, so that the data on disk is now guaranteed to not match the checksum on disk.

Without something like the above sequence of events, I don't see how ECC eliminates any class of errors, rather than just reducing their probability. So what actually triggers such a chain of events?

-----


http://en.wikipedia.org/wiki/Panspermia

-----


Panspermia has nothing to with where the water came from.

-----


http://www.nature.com/news/dna-has-a-521-year-half-life-1.11...

DNA has a 'half-life' of ~500 years. Panspermania may still be a viable theory, but it is very restricted in terms of stellar distance/time in transit.

-----


That's at (or near) STP, though.

-----


Very true, but getting this data in a vacuum and in a stellar radiation environment is tough. Who knows what the preserving effects of space are like to DNA. However, one data point is better than none.

-----


What's STP?

-----


Probably "Standard Temperature and Pressure":

http://en.wikipedia.org/wiki/Standard_conditions_for_tempera...

-----


You should maybe tell them to remove their own "google cache" version as well...

-----


The other way around. The link you gave is a duplicate of this post actually.

-----


Here is the HN post from yesterday that also points to the NYTimes article: https://news.ycombinator.com/item?id=8621658

-----


OK – this post has a higher ID than the other one; I assumed they were assigned sequentially.

-----


How does Terraform compare to e.g. Mesos? Or am I comparing apple and oranges here?

-----


I'm guessing its this. https://www.youtube.com/watch?v=YUhUzUWOIug

-----


Relevant:

http://h5bp.github.io/Effeckt.css/

http://h5bp.github.io/Effeckt.css/off-screen-navs.html

-----


How does Go.cd measure up against e.g. Jenkins or Hudson?

-----


The answer to this question probably deserves a blog post. But, as mentioned by @willejs here (https://news.ycombinator.com/item?id=7646496), Jenkins has a well established community of plugins and plugin writers and so, is quite extensible. Go has good visualisation and good modeling capability, allowing you to model complex build and deployment workflows using a combination of tasks running in parallel and serial.

Both have many more pros and cons. To do justice to it, it needs a blog post. Let's see. Maybe I'll write one soon.

EDIT: This mailing list post has some more information: https://groups.google.com/forum/#!searchin/go-cd/jenkins/go-...

-----


Here's a google group topic talking about it. https://groups.google.com/forum/#!searchin/go-cd/jenkins/go-.... Hope it helps.

-----

More

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: