I've got a question that i've wondered for a while and before maybe contacting HP on it I thought I would hear what self-experience on your behalf would say about it.
I have Service Desk application Server installed on a 3,2Ghz Pentium with 4,0 GB of memory on a Windows Server 2003 and nothing else running on that server other than Service Desk ( even Service Pages are on another server ). The database is running on a separate server with more than enough bandwidth between each other.
On a normal situation there are between 80 to 100 users connected via Service Desk client and another 100 through Service Pages.
What I was wondering is what are the Service Desk limitations to this kind of hardware in terms of Service Calls, CIs, Persons, Connected Users, etc
Just checking if it would be good to start thinking about some load balancing.
We have a daily growth of around 200 new service calls per day and 100 workorders. Total right now in the database is 20.000 workorders and more than 30.000 service calls.
I have some documentation regarding service desk load balancing handed out at the last HP Universe in Vienna but what would you guys recommend as a limit for a single application server so that I can estimate "how much" load balancing it takes to optimize the current situation ?
Another aspect of the equation is the number of rules and scheduled tasks. Too many rules in a given module increases the amount of time it takes to save and process each item while increased numbers of scheduled tasks consume memory.
HP has told us that each server should have no more than 10,000 scheduled tasks although we've think that the threshold for optimum performance is around 5,000 scheduled tasks.