Let me explain a bit.
My main task is
To review for senior management if can get the performance we need out of Couchbase before we commit to this solution.
Our requirement is for 10K concurrent users what kind of a cluster we will need.
Any suggestions on what i can do to get a baseline of what can i get out of Couchbase / Java SDK for the following set-up.
I’m interested to better understand the limits for database access (read/write/query) via Java SDK and Couchbase for a small cluster
( 4 cores each node 1 data/ 2 index/ 1 query ) with 6 indexes for N1QL and 1 million documents or something similar if any official benchmarks I can see on the Java SDK with Couchbase can also help .
Some information on what I am doing,
Basically we have messos cluster with Wildlflies (Jboss) with Rest API that use stateless EJBs pool that then hit the couchbase DAO that uses CB Java SDK and that hits CB Database.
I am testing/trying with different scenarios of concurrent API calls / Wildlfy thread pool numbers / Ejb pool numbers …
We find that increasing the concurrent Restful API calls to 5K - 10K for example on a logon operation
we get the 2 error I previously sent . Thus I assume what the DefaultCouchbaseEnvironment needs tweaking or
we have reached the limits of the our stack . This is what I don’t know and I don’t want to make an assumption as to make my conclusion wrong .
Any help is welcome .