Hi Ramakrishna,
> I could see everyone using Hazecast, in my case is Redis a bottleneck?
Using hazelcast is for ease of setup and also the fact that I saw many
people already using it.
I am a believer of "if it ain't broke don't fix it", so unless you actually
sees a problem in performance, imo d
Hi Dave,
Nice question.
1. Redis
2. 5
3. 3
4. Different
5. 80k
6. Have started load-testing last week & have reached 10k per day till now.
No problem yet.
Bryan / Ray / Andy
I could see everyone using Hazecast.
In my case is Redis a bottleneck? However, until now for 10k login load, I
have not
Hi Dave,
1. Hazelcast
2-5. I consider them sensitive information, sorry Dave can't disclose them
6. You might need to the cap the memory or else it will use a large
percentage of the memory,
and there is more network traffic between the servers then we expected (but
ultimate is still stable s
1. Hazelcast
2. 4 round robin
3. 4
4. Same server
5. 40k per day (all users)
6. No issues
Our previous install used ehcache. It did not replicate fast enough to support
round robin so we used primary and fail over.
Hazelcast is not replicated (at least not by default). It has stood up
admirably
1, Hazelcast
2. 4
3. 4
4. Same server
5. 200k per day using Duo (employees) Students add more. I have seen 400k
total per day.
6. No issues
Bryan
University of Utah
On Fri, Feb 22, 2019 at 10:12 AM wrote:
> Hi everyone,
>
> A few questions for those of you who are using a distributed or high
>
Hi everyone,
A few questions for those of you who are using a distributed or high
availability CAS implementation (i.e., more than one server in a pool of
some sort):
1. Which technology are you using for your ticket repository?
2. How many CAS servers are you running?
3. How many tick
