|Re: [geomesa-users] Performance Issue?|
Thanks for replying, We have 3 tablet servers and used gdelt data between 1979 to 2005 and we are querying Accumulo through GeoServer with following url type:http://localhost:8090/geoserver/wfs?service=wfs&version=2.0.0&request=GetFeature&typeNames=geomesa:gdelt&bbox=73,31,74,32
Here bbox values are changing for each query.We have bench marked response of GeoServer with Siege and following are the results:Transactions: 4595 hitsAvailability: 99.93 %Elapsed time: 599.89 secsData transferred: 1.27 MBResponse time: 1.42 secsTransaction rate: 7.66 trans/secThroughput: 0.00 MB/secConcurrency: 10.87Successful transactions: 4595Failed transactions: 3Longest transaction: 11.12Shortest transaction: 0.02Here longest transcation is taking around 11.12 seconds which is too much for real time querying because we are thinking of doing a lot of queries and we require response in miliseconds. Can we achieve that?Regards,Adnan and OthersOn Thu, May 22, 2014 at 7:50 PM, Hunter Provyn <fhp@xxxxxxxx> wrote:
We have dealt with 5.5 billion record tables.
How many tablet servers are in your deploy environment?
What queries are taking too long for you? This is through geoserver and not through the Java API, right?
On 05/22/2014 12:18 AM, Adnan Yaqoob wrote:
We are new to geomesa so please bear with us, we are trying to use geomesa for our road congestion information. Our question here is can we use geomesa for real time query performance, right now when we query gdelt data in accumulo through geoserver, It is taking too much time. Will it work with real time performance requirements.
We have tested geomesa on 3 node cloudera cluster. We are using Accumulo 1.6.0 and geomesa 1.0.0-SNAPSHOT (Latest).
Regards,Adnan and Others
_______________________________________________ geomesa-users mailing list geomesa-users@xxxxxxxxxxxxxxxx http://www.locationtech.org/mailman/listinfo/geomesa-users
Back to the top