mahout-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pricila rr <pricila...@gmail.com>
Subject Re: Jobs Hadoop-Mahout: Full Capacity
Date Sat, 10 Nov 2012 19:28:57 GMT
No, as is the default

2012/11/10 Sean Owen <srowen@gmail.com>

> Did you set -Dmapred.reduce.tasks ? it defaults to 1.
>
>
> On Sat, Nov 10, 2012 at 7:22 PM, pricila rr <pricilarr4@gmail.com> wrote:
>
> > I am running kmeans algorithm.
> > Increasing the number of tasktrackers and datanodes, increase the speed?
> >
> > Thank you
> >
> > 2012/11/10 Dmitriy Lyubimov <dlieu.7@gmail.com>
> >
> > > I would imagine optimizing Mahout jobs are not fundamentally different
> > from
> > > optiimizing any Hadoop job. Make sure you have optimal amount of task
> per
> > > node configured, as well as optimal amount of memory to prevent GC
> > > thrashing. (Iterative Mahout batches tend to create GC churn at
> somewhat
> > > respectable rate). When optimized correctly, individual Mahout tasks
> tend
> > > to be CPU bound.
> > >
> > > Could you tell which Mahout method specifically you are talking about?
> > >
> > >
> > > On Sat, Nov 10, 2012 at 11:11 AM, pricila rr <pricilarr4@gmail.com>
> > wrote:
> > >
> > > > Hello,
> > > > How to run jobs on Hadoop-Mahout, using processor full capacity?
> > > > I have 10 slaves and 1 master, with i5 CPU. But the jobs
> Hadoop-Mahout
> > > not
> > > > use all this capacity.
> > > >
> > > > Thank you,
> > > > Pricila
> > > >
> > >
> >
>

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