hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 杨浩 <yangha...@gmail.com>
Subject test YARN
Date Mon, 15 Dec 2014 14:00:20 GMT
Hi,in the paper "Apache Hadoop YARN: yet another resource negotiator",
there is a sentence
        After over 36,000 years of aggregated compute-time and
several months of production stress-testing, Yahoo’s operational team
confirms that YARN’s architectural shift has been very beneficial for their
workloads

This is interesting. I'm wondering how the 36,000 year come out, and what's
the meaning of  aggregated compute-time ?

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message