this message in context:
http://lucene.472066.n3.nabble.com/Server-sizing-Hadoop-Mahout-tp3986807.html
Sent from the Mahout User List mailing list archive at Nabble.com.
Hi Sean! First of all, thanks for your reply!
I do agree that it's very complicated to do the sizing of an environment since
The problem with this POV is that it assumes it's obvious what the
right outcome is. With a transaction test or a disk write test or big
sort, it's obvious and you can make a benchmark. With ML, it's not
even close.
For example, I can make you a recommender that is literally as fast as
you like
as a baseline.
So I’d be pleased if someone can help me.
Thanks in advance.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Server-sizing-Hadoop-Mahout-tp3986807.html
Sent from the Mahout User List mailing list archive at Nabble.com.
but, in example,
in
Application servers or Web Servers normally sizing is done inferring
hardware needs using some benchmarks as a baseline.
So I’d be pleased if someone can help me.
Thanks in advance.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Server-sizing-Hadoop
