values of these parameters

[T G Manikandan]

I have these disks mixed
18GB ST318404LC 33 MB/s
18GB ST118202LC 17 MB/s

>>how often are they done? What is the purpose of them? How critical is performance of the resulting binaries? Would reducing the optimization level of the compilations be an option?

The compilations are infact done on a daily basis and shipped to the client.


Yes we are supporting the Banking software.
When there is a spec change or something all the sl which have got changed are again complied and shipped to the client.
As these sizes of the compilation files are huge they take long hours to complete.

I know there is sure a memory crunch on some of my L-class servers.

The steps we have taken is that

1.Application was tuned for unwanted code.
2.Incremental builds were carried on.
3.The sl were grouped and the 4 simultaneous processes were run.
Actually there is very big time difference avoided due to this split and simultaneous fire of jobs on the unix system.
5.Also these were equally distributed so that all the processes complete at the same time.
6.There are 4 to 5 process compilations are carried over.
Each process takes 20 hrs to complete and the entire build completes in that time.
Using glance I could see a large memory usage.
Infact each process using around 500MB on the machine.

There is no nfs involved in this process.


Thanks

[T G Manikandan]

This is from hp tuning guide

//*

ninode
Ninode sizes the in-core inode table, also called the inode cache. For performance, the most recently accessed inodes are kept in memory. Each open file has an inode in the table. An entry is made in the table for each "login directory", each "current directory", each mount point directory, etc. It is recommended that ninode be set to 15,000.

NOTE: On a multi-processor system running HP-UX 10-20, ninode should NOT exceed 4000. This is due to a spinlock contention problem that is fixed in 11.0.

*//

http://docs.hp.com/hpux/onlinedocs/os/11.0/tuningwp.html

[T G Manikandan]

I feel that hp tuning guide has taken a very high end machine with huge resources that the parameters are so high.

Arent they?