thanks jack, let me know how your testing goes!
On Fri, Dec 26, 2014 at 11:57 AM, Jack Park jackp...@topicquests.org
wrote:
On my platform, there is one and only one es client, through which all
requests go. It seems to work well, though well is defined as having just
a few people using it at
no answer, so let me ask a different way. how are most of the es
javascript client apps managing the instance of the client?
do you have one es client per app (singleton) that all requests go
through? Do you create and destroy clients for every request? Do you use
a es client pool using
On my platform, there is one and only one es client, through which all
requests go. It seems to work well, though well is defined as having just
a few people using it at one time. We plan to start stress testing the
system soon.
Cheers
Jack
On Fri, Dec 26, 2014 at 9:55 AM, phil swenson
I'm writing a node/es app using the es javascript api
Is there any reason to use pooling for all the javascript clients? Or
should I just use one client for the app?
Thanks,
phil
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To