I've got a curiousity. How can I determine with some accuracy the ability of an Essbase Agent to handle transactions? Considering all of the reasons a user base of say... 50-100 concurrent users might need to login, logout, set active, etc. How can I calculate the transactional throughput without harnessing Load Runner and forcing it to crash?
A. does it matter if I have externalized the users or not?
B. does it matter how complex / how many security filters I have or not?
What is the process for turning an agent thread into a database thread? How independently do they operate?
I would suggest you just set the threads settings and be done with it.
That user load is not too crazy.
Try below in your essbase.cfg:
; 60 current transactions within single APPLICATION (ESSVR.EXE)
; 75 threads handling 1423 (ESSBASE.EXE)
; Carol Crider communicates devleopment says 10 Agent Server is maximum. More are bad.
Each thread takes up 1-2 MB of ram (you can google exact)
John A. booth