Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
MapReduce, mail # user - Why they recommend this (CPU) ?


+
Patai Sangbutsarakum 2012-10-11, 16:22
+
Jay Vyas 2012-10-11, 17:46
+
Russell Jurney 2012-10-11, 17:56
+
Ted Dunning 2012-10-11, 18:38
Copy link to this message
-
Re: Why they recommend this (CPU) ?
Russell Jurney 2012-10-11, 19:03
My own clusters are too temporary and virtual for me to notice. I haven't
thought of clock speed as having mattered in a long time, so I'm curious
what kind of use cases might benefit from faster cores. Is there a category
in some way where this sweet spot for faster cores occurs?

Russell Jurney http://datasyndrome.com

On Oct 11, 2012, at 11:39 AM, Ted Dunning <[EMAIL PROTECTED]> wrote:

You should measure your workload.  Your experience will vary dramatically
with different computations.

On Thu, Oct 11, 2012 at 10:56 AM, Russell Jurney
<[EMAIL PROTECTED]>wrote:

> Anyone got data on this? This is interesting, and somewhat
> counter-intuitive.
>
> Russell Jurney http://datasyndrome.com
>
> On Oct 11, 2012, at 10:47 AM, Jay Vyas <[EMAIL PROTECTED]> wrote:
>
> > Presumably, if you have a reasonable number of cores - speeding the
> cores up will be better than forking a task into smaller and smaller chunks
> - because at some point the overhead of multiple processes would be a
> bottleneck - maybe due to streaming reads and writes?  I'm sure each and
> every problem has a different sweet spot.
>
+
Patrick Angeles 2012-10-11, 19:36
+
Goldstone, Robin J. 2012-10-11, 19:47
+
Ted Dunning 2012-10-11, 19:56
+
Steve Loughran 2012-10-12, 08:19
+
Russell Jurney 2012-10-13, 07:22
+
Aaron Eng 2012-10-11, 19:15