No, I don't see CPU utilisation going 100% (reaches upto ~40%). Here is the accumulo table data size: Table Name - aj_join aj_join_attr_v4 <http://localhost:9995/tables?t=1f> - 79.79MB aj_join_records_v2 <http://localhost:9995/tables?t=1e> - 58.25 MB
Scan(Entries/s) goes to - 200000 Disk Usage shows - ~10Mbps for Read while scan rate on Accumulo web interface is very less. Here is the screen shot for the same On Mon, May 1, 2017 at 8:22 PM, Keith Turner <ke...@deenlo.com> wrote: > Do you know if the tablet server and/or client is CPU bound? When you > run the query, do you see either go to 100% CPU? > > For the *~1 million* records, what is the data size? I Ask because I > am curious what the data rate is? For example is it 2MB/sec > 500KB/sec? > > On Thu, Apr 27, 2017 at 7:09 AM, Suresh Prajapati > <sureshpraja1...@gmail.com> wrote: > > Hello Team > > > > I am developing a client in accumulo to store geo-spatial information and > > using geomesa for indexing on top of it. However i found that scanning > *~1 > > million* records taking *2-3 sec*. I looked at indexes and query plan of > > geomesa but not able to find cause of the problem. I am running accumulo > as > > single tablet-server(including master). I want to know - > > what are the factors can affect accumulo scanning operation? how can I > > optimise this time? > > > > Thank You > > Suresh Prajapati >
