Why are you using a print writer to get output from your iterator? Just
use a logger and look in $ACCUMULO_HOME/logs/tserver_$hostname.debug.log
(or wherever you configured logging). Create a log4j or slf4j Logger and
use that instead of a print writer. (It's possible that your print
writer is also what is slowing things down)
In most real deployments, iterators should be faster on the server side
than your client because you have N servers performing the work instead
of your one client.
It's not unheard of that a programming error is slowing down your
iterator. Looking at what your iterator does (via logging) should help.
Alternatively, you can use a remote debugger, connect a the
tabletserver, and set breakpoints inside your iterator.
shweta.agrawal wrote:
On Monday 30 March 2015 09:58 AM, shweta.agrawal wrote:
Hi,
Actually i am working on iterator, which i ran on server side by
making jar and also on client side on same data, but on server side
jar which i made is working slow than on client side. I am not able to
find what went wrong. is it possible to work same logic more fast on
client side than on accumulo iterators?
time on client side:8s
time on server side:30s
And to get the output i am writing output on text file through print
writer. To perform my task, i am calling my method on next method and
i am writing output to a file in next method. So actually i want to
know the final method which is called, so that i can write my output
to a file after performing all the task.
Thanks and Regards
Shweta
