Agree, I am not sure if it adds value to publish an AMI that just adds a copy of the Mahout distro. What I was thinking of for my part is a minimal OS plus Java plus Mahout with a startup script that runs the processing, then shuts down automatically. The AMI would not be extended, but invoked with parameters, kind of like an RPC.
Using Hadoop involves a large jump in overhead. It is of course necessary at some scale to move to this framework. But I would like to provide a one-big-machine solution for small- and medium-sized users since it will be a lot simpler and more cost effective. On Mon, Feb 2, 2009 at 5:57 PM, Ted Dunning <[email protected]> wrote: > Based on my experience moving our search engine to work in the cloud, I > would say that it would be easier on users to not actually build a > specialized AMI, but rather to make some publicly available S3 resources > such as an installation script, jars and tars. > > That allows people to install and run mahout not just on a single AMI, but > also on any AMI they are running. It also makes it easy for anybody else to > use Mahout fairly trivially.
