topic Re: Expanadbility in Operating System - HP-UX

Expanadbility

Paula J Frazer-Campbell — Thu, 02 Aug 2001 10:26:09 GMT

Hi to all

I am currenty looking at limits for expandability on a N class running 11.00.

Max limits can be set in kernel, but what are the max number of telnet sessions, ftp sessions etc that a fully loaded (8 x 550 Mhtz and 32 Gb RAM) can run.

Basically things like 2GB on files can cause problems for tar etc, but what about pttys and systems that control the actual connectivity to the server.

Paula

Re: Expanadbility

Carlos Fernandez Riera — Thu, 02 Aug 2001 11:15:01 GMT

I guess your using a Oracle database.

To configure your box for large users you must configure

maxusers ,

maxproc , maxuproc,

maxfiles, nfiles

nfslock,
npty
nstrpty
nstrtel

maxswapchuncks

Maxusers is used to set some of these values, so increase first this parameter.

Re: Expanadbility

Paula J Frazer-Campbell — Thu, 02 Aug 2001 12:33:43 GMT

Hi Carlos
Thanks for the reply: -

What I am looking at is things like if I try to telnet 10,000 times to the server at what point will it stop and say cannot allocate specific recourses, for example it will not allow any more telnetd to run of allocate ptty.

I think I should have rephrased my question better.

Paula

Re: Expanadbility

Carlos Fernandez Riera — Thu, 02 Aug 2001 17:46:03 GMT

Hi Paula:

I know my response was very sort, but it was a fast response, and 2 it was the first response.

For 10.000 telnet sessions you should configure npty as 10.000

But 10.000 telnets needs 10.000 process plus 10.000 sh -> at least maxproc = 20.000

Each process use to open 3 standard files -> nfiles=60.000

And so on.

If I recall well sysdef command list actual ,min and max values accepted by kernel.

My preference is SAM, to tunnig.

Better now?

Re: Expanadbility

Wodisch — Wed, 08 Aug 2001 11:10:29 GMT

Hello Paula,

in addition to what Carlos wrote, accessing your system
over the network means usually BSD pseudo ttys, plus
System V pseudo ttys, plus TELNET pseudo ttys, and for
each you will need a master and a slave device.
So we are talking about about a maximum of about
65000 TCP connections concurrently, which would need
65000 * 3 * 2 inodes for those device in your root-fs!
I do remember a customer having a setup like this,
and they had to install specifically for these conditions
(well, that was in the days of HFS for root-fs). Still this
needs an awful lot of inodes, file-entries, processes,
timers (ncallout) and such in your kernel, so the next
step will be to install the patch to boot "large kernels",
which is needed at a certain size of your kernel (I do
remember 79MB for the V-classes, for the others it was
way smaller, something like ~32MB).

And you will need many, many LAN interface cards, to
spread the burden, perhaps even APA (port trunking).

Ask your hp-supporters for more ramifications, as there
are propably many more :-(

HTH,
Wodisch

Re: Expanadbility

nancy rippey — Tue, 23 Apr 2002 13:06:26 GMT

You will probably want to increase your swap if you are adding memory. Along with this you would want to increase maxswapchunks.
maxswapchunks

maxswapchuncks
This (in conjunction with some other parameters) sets the maximum amount of swap space configurable on the system. Maxswapchunks should be set to support sufficient swap space to accommodate all swap anticipated. Also remember, swap space, once configured, is made available for paging (at boot) by specifying it in the file /etc/fstab (/etc/checklist on 9.X). The maximum swap space limit calculated in bytes is: (maxswapchunks * swchunk * DEV_BSIZE). We recommend this parameter be set to 4096.

Hope this helps

Re: Expanadbility

nancy rippey — Tue, 23 Apr 2002 13:07:08 GMT

sorry wrong thread

nancy