multiple users for an application (?)

[Tim Howell]

I have written a relatively simple application using Oracle Pro*C, which is just a precompiler that turns the Oracle calls into c code that gets compiled and linked by the HP-UX products. It is running on HP-UX 11i (64 bit) and interacts with Oracle 8i. Is there anything in terms of system resource management I need to include in order to have multiple concurrent users? I viewed this like 20 users logging in and running "top" or something. Is this an oversimplification? I know Oracle handles all the database calls, but I was wondering about things like shared memory, file usage, etc. Currently I am using only stack space (not heap) and am not using file I/O (I said it was simple...) Is there a good resource for this information if I do need to use it?
Thanks in advance!!!

[Leif Halvarsson_2]

Hi,
If this is a relative simple application and a limited number of users I don,t think you need to modify any system parameters. There is a number of tools (for example vmstat and GPM) which you can use to monitor system activity.

[Christopher Caldwell]

On the client side, the client code is subject to all of the normal resource constraints - e.g. if the client is compute intensive, it'll look compute intensive on the client host.

On the database side, there are a number of tunes you have to look at - the tunes cap the resources available to things like the client processes. For example, the number of connections (processes) for Oracle; there are also memory constraints, etc.

If the client host and the database host are the same, then add paragraph 1 and paragraph 2.

[A. Clay Stephenson]

You need to do things like: How many files handles will be open by each application? - in addition to all the routine needs of the OS. Will nfile thus need to be increased? Will any one of my applications need many files opens so that I need to look at maxuprc?

How much memory does each process use? (some of it's shared like text/shared library) - so don't count more than once but some is unique to each process. Do I have enough memory so that the box is not driven into swapping.

Having said all this, pulling 20 small applications is really nothing. The one red flag that I saw was your statement that you use only stack space. This implies that you are running static arrays. Generally, that's a bad thing. You either make them big, safe - and wasteful or they are undersized -requiring a compile to fix things. The better technique is to learn to use dynamic allocation and allow you arrays to grow "on the fly".