Forget to say. I also tested MapReduce. It's faster than coprocessor.
On Mon, Feb 18, 2013 at 10:01 AM, yonghu <yongyong...@gmail.com> wrote: > Parkash, > > I have a six nodes cluster and met the same problem as you had. In my > test, inserting one tuple using coprocessor is nearly 10 times slower > than normal put operation. I think the main reason is what Lars > pointed out, the main overhead is executing RPC. > > regards! > > Yong > > On Mon, Feb 18, 2013 at 6:52 AM, Wei Tan <w...@us.ibm.com> wrote: >> Is your CheckAndPut involving a local or remote READ? Due to the nature of >> LSM, read is much slower compared to a write... >> >> >> Best Regards, >> Wei >> >> >> >> >> From: Prakash Kadel <prakash.ka...@gmail.com> >> To: "user@hbase.apache.org" <user@hbase.apache.org>, >> Date: 02/17/2013 07:49 PM >> Subject: coprocessor enabled put very slow, help please~~~ >> >> >> >> hi, >> i am trying to insert few million documents to hbase with mapreduce. To >> enable quick search of docs i want to have some indexes, so i tried to use >> the coprocessors, but they are slowing down my inserts. Arent the >> coprocessors not supposed to increase the latency? >> my settings: >> 3 region servers >> 60 maps >> each map inserts to doc table.(checkAndPut) >> regionobserver coprocessor does a postCheckAndPut and inserts some rows to >> a index table. >> >> >> Sincerely, >> Prakash >>
