We wish to deploy a web based infrastructure using version 7.0.2 for applications (other than application routing no mail will be hosted on this system), is anyone aware of any sizing guides that might be applicable to this typr of scenario?
Subject: Sizing Guides for Web Based Application Infrastructure
Joanne,
Do you mean, “How many concurrent users could such a server support?” If so, your application design will cause really major fluctuations in that number. For example, suppose you have a really small and simple application that gets a fair number of hits of people reading documents with the MAIN form. No big deal, right? But now suppose you put a WebQueryOpen agent on that form. Suddenly, your server might be thrashing as it tries to execute hundreds or thousands of concurrent executions of that agent.
This is something that might be considered really benign in a Notes environment, but because of some subtle differences in how we run code for web apps (server vs client for code in this example) it can have major implications on performance.
One of the best features of Domino is that you have such flexibility for coding, and that you can change the code so quickly and easily. But this brilliant feature also means that it’s very hard to measure applications for performance.