topic Re: X server limits in Operating System - HP-UX

X server limits

Eric Rainer — Tue, 30 Apr 2002 08:50:59 GMT

Hello
I am trying to scale a display server(HP-UX 11). Users will login the system and get remote X-11 sessions send to their display. Are there X-11 limits. I.e. how many X-11 connections can the server have. ?

thanks
Eric

Re: X server limits

Steve Steel — Tue, 30 Apr 2002 08:59:52 GMT

Hi

The dtlogin is only a process for the system and as such there are no limits on the X connections.

If your system allows enough processes then it is fairly endless.

assuming you use CDE

check /var/dt/Xerrors and $HOME/.dt/*log for faults and
/etc/dt/config/* /usr/dt/config/* for the setups

/etc is the original and should be copied to /usr if changed

Steve Steel

Re: X server limits

Santosh Nair_1 — Tue, 30 Apr 2002 09:07:14 GMT

One thing to remember is that the X-Server is the software running on the client machine, i.e. if I send a X display back to my machine, I should have an X server running on my machine willing to accept the display. So for example if your client machine is a PC and they want to get X display from a HP server, the X server should be running on the PC.

With regard to your question though, the server is only limited by the max number of processes that can run on the machine, i.e. kernel parameters nproc and maxuprc.

Hope this helps.

-Santosh

Re: X server limits

Alex Glennie — Tue, 30 Apr 2002 09:20:36 GMT

fire up sam -> DISPLAY -> Xsever Configuration see Max number of file descriptors ..... default = 192 max = 374 the help section in sam has a good explanation.

also you may want to take a look at the GSMT & SMT settings sizes again viewable under Xsever config.

other than that normal kernal parameters will also ned to be tuned maxusers etc ....

Re: X server limits

Wodisch — Tue, 30 Apr 2002 10:36:36 GMT

Hello Eric,

the *possible* number of X-connections is your least problem:
- each CDE session eats up vast amounts of virtual address space (i.e. swapspace)
- each CDE session eats up at least about 32MB of RAM
- in each session usually a lot windows and hence processes are used
- everything should be pretty interactive or your users will complain, so you will need multiple CPUs, and fast ones
- X-Windows is a bandwidth hog, so make sure you have multiple LANICs, and fast ones, and your users are evenly spread over those

Just my $0.02,
Wodisc