On Samstag, 25. Juni 2011 at 00:23, David Mitchell wrote: > Hi Mathias, > > Thank you for responding, and give me things to try. > > I am testing Raik using a hypervisor, so each node only has one CPU and 1.5 > GB of RAM. I have 222,526 total keys stored. > I'd suggest testing your setup on something other than a hypervisor'd setup of virtual machines to get a good picture of performance, especially at this memory and machine size. > Correct me if I am mistaken, but if we want to use Riak for data processing > via MapReduce, we should abandon JavaScript and opt for Erlang. This is my > first take away. Second, use Riak Search rather than key filters to do range > queries. > Considering your key filter setup, yes, you should be using Riak Search instead to prefilter your MapReduce inputs. As for MapReduce itself, it's well worth looking into Erlang, because it avoids a lot of overhead involved with JavaScript MapReduce. I wouldn't hold it generally true to always go for Erlang for more intensive MapReducing, it just depends on how often you run your queries and what execution speed expectations you have of them. In your case I'd say it'd be well worth looking into Erlang as an alternative.
Mathias Meyer Developer Advocate, Basho Technologies _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
