Essbase Agent Capacity Planning (9.3.1)

Essbase Agent Capacity Planning (9.3.1)

Old Hack
Old Hack

April 19th, 2012, 6:40 pm #1

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?

Additionally,
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?
Quote
Share

John A. Booth
John A. Booth

April 20th, 2012, 12:37 am #2

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)
SERVERTHREADS 60
; 75 threads handling 1423 (ESSBASE.EXE)
AGENTTHREADS 75
; Carol Crider communicates devleopment says 10 Agent Server is maximum. More are bad.
AGTSVRCONNECTIONS 10

Each thread takes up 1-2 MB of ram (you can google exact)

Regards,

John A. booth
http://www.metavero.com
Quote
Share

Old Hack
Old Hack

April 20th, 2012, 1:54 am #3

I'm sure that Crider is right. We were not thinking of changing AGTSVRCONNECTIONS as ther is no APS I the stack. It is all pure Excel.

SERVERREADS is already high. My attitude is the same as yours - just bump up yhe setting - why ask why? but my customer is anxious for a theoretically correct answer.


Thx.
Quote
Share


Confirmation of reply: