These agents can exist on the same physical machine. No need to put in
zones. If you have 4 agents and 2 driver machines, each driver machine
will automatically run 2 agents. Each agent is just a Java process.
There is a way to force different load distribution than equal balancing
but I won't go there unless you need it.
-Akara
Brian Overstreet wrote:
I think I will use zones to have multiple agents on the same machine.
With 2000 users spread over 3 agents on 3 machines, the load on the
target is only 40%. By putting several agents on zones I should be able
to scale up without hitting that limit.
Thanks,
Brian
Akara Sucharitakul wrote:
We are looking at some possible memory leaks, but cannot yet isolate
them whether these are Faban issues, our workload driver issues, or
some library issues. Not even sure they are memory leaks just yet.
Based on experience with this workload, I'd suggest running up to ~700
concurrent users per agent if you're running the agents in a 32 bit
address space. Just increase the number of agents. At 1500 concurrent
users, I suggest 3 agents (although you may be able to survive with
2). The load will be evenly distributed among agents.
-Akara
Brian Overstreet wrote:
With the current architecture of Faban and Olio, are there any known
limits on the number of concurrent users? When I scale the number of
users up to 1500 per agent, the JVM running the agent crashes. I was
wondering if other people have had higher numbers per agent. This might
be more relevant to the faban list, but I'll start here.
Thanks,
Brian
