| Re: [geomesa-users] Performance Issue? |
Another recommendation is to enable the JAI extensions to improve Geoserver's rendering speed. Check out the following blog post:
http://docs.geoserver.org/stable/en/user/production/java.html#install-native-jai-and-jai-image-i-o-extensions
On Fri, May 23, 2014 at 12:15 PM, Chris Eichelberger <cne1x@xxxxxxxx> wrote:
Adnan,
My guess is that querying with 1 square-degree search-polygon against a
~250 million record data-store backed by 3 tablet-servers, all going
through GeoServer, is not likely to yield significantly better
performance than what you are currently seeing.
To improve the performance, you might consider one or more of the
following:
* increase the number of tablet servers; because the queries are
distributed uniformly across the available tablet-servers (by default),
this may decrease the mean response time
* issue queries in your own code, bypassing GeoServer; this will give
you the raw iterator of SimpleFeatures faster, but will not give you the
visualization, so this may not be useful, depending on your need
* if any of your Accumulo nodes are VMs, you could consider replacing
them with dedicated hardware
* tweak Accumulo settings for index-, data-block caching and block-cache
size
* if repeat queries are common in your application, consider enabling
some sort of cache; GeoWebCache is available within GeoServer as one
possibility
There are many other approaches that might help to improve response
time, but -- depending on your application -- they may or may not be
applicable.
I hope this helps. If not, please just let us know.
Thanks!
Sincerely,
-- Chris
_______________
Chris Eichelberger,
Commonwealth Computer Research, Inc.
434-284-9422 (work)
On Fri, 2014-05-23 at 13:24 +0500, Adnan Yaqoob wrote:
> Previous benchmark transaction was equal to 10 concurrent connections
> to server, following is single connection to server benchmark:
>
>
> Transactions: 826 hits
> Availability: 99.88 %
> Elapsed time: 599.61 secs
> Data transferred: 0.23 MB
> Response time: 0.21 secs
> Transaction rate: 1.38 trans/sec
> Throughput: 0.00 MB/sec
> Concurrency: 0.28
> Successful transactions: 826
> Failed transactions: 1
> Longest transaction: 1.04
> Shortest transaction: 0.01
>
>
> Here Longest transaction is around 1 second, can we ensure milisecond
> query response for single or multiple queries at a time?
>
>
> Regards,
> Adnan and Others
>
>
> On Fri, May 23, 2014 at 12:40 PM, Adnan Yaqoob <nsyaqoob@xxxxxxxxx>
> wrote:
> 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 hits
> Availability: 99.93 %
> Elapsed time: 599.89 secs
> Data transferred: 1.27 MB
> Response time: 1.42 secs
> Transaction rate: 7.66 trans/sec
> Throughput: 0.00 MB/sec
> Concurrency: 10.87
> Successful transactions: 4595
> Failed transactions: 3
> Longest transaction: 11.12
> Shortest transaction: 0.02
>
>
> Here 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 Others
>
>
> On Thu, May 22, 2014 at 7:50 PM, Hunter Provyn <fhp@xxxxxxxx>
> wrote:
> Adnan,
>
> 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?
>
> Hunter
>
>
> On 05/22/2014 12:18 AM, Adnan Yaqoob wrote:
>
> > Hello,
> >
> >
> > 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).
> >
> >
> > Thanks.
> >
> >
> > Regards,
> > Adnan and Others
> >
> >
> >
> > _______________________________________________
> > geomesa-users mailing list
> > geomesa-users@xxxxxxxxxxxxxxxx
> > http://www.locationtech.org/mailman/listinfo/geomesa-users
>
>
>
>
>
>
> _______________________________________________
> geomesa-users mailing list
> geomesa-users@xxxxxxxxxxxxxxxx
> http://www.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
http://www.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
http://www.locationtech.org/mailman/listinfo/geomesa-users