Common resources in HP-UX 11 environment

[Enrico Venturi]

Dear all,
a just theoretical question:
I want to run several application on my system; what are the common resources to be monitored in order to check if there are mutual interferences? i.e. directories, files, semaphores, etc.
Where I have to look in order to detect side effects from the application co-hosting?
thank you
Enrico

[harry d brown jr]

Enrico,

You need to have intimate knowledge of the existing applications on the system and you need to know the demands that the new application will place on the server. Without this knowledge you are just spitting into the wind.

Capacity planning requires a lot of knowledge about everything, and it requires tools like glance/measureware & perfview.

You need to know the amount of memory every user needs, IO rates, cpu demands, then you need to determine how they will exist within the current system. You need to look at number of inodes, files open, nproc, maxusers, and just about every other kernel parameter.



live free or die
harry

[Enrico Venturi]

Thanks for the replies but they are not what I were looking for.
I didn't clearly explain my problem:
I have two applications who run stand-alone; I validate their behaviour, it's OK!
Now, I want to co-host them: no problem about performances! the HW is powerful enough! My concern is about the conflict on using common resources, e.g. the same semaphore, or the same socket, or something else.
My question is: what are the parameters I can / I have to check in advance to detect possible conflicts?

Thanks again!!

[Jeff Schussele]

Hi Venturi,

Unless the applications use the exact same /path/to/filenames, I don't think you need to worry *too* much.
The only gotcha I can think of immediately is if one is a resource hog & will starve the other. But this can be mitigated with kernel parms that will limit what a single process can get as a maximum.
The kernel will oversee the allocation of memory, semaphores, etc & will keep track of them.
As to sockets, one way to avoid any contention would be too assign different IPs to each app. Even if you have only one NIC in the system you could assign a virtual IP to the 2nd app - EX
app1 => lan0 => 111.222.111.222
app2 => lan0:1 => 111.222.111.223
Then the sockets would always be unique & distinct.

Rgds,
Jeff