HP Visualize J5000 hp workstations - hp-ux 10.20 graphics administration guide - Page 35

Performance Tuning of SMT, Under most circumstances this should be unnecessary.

Get HP Visualize J5000 - Workstation PDF manuals and user guides View all HP Visualize J5000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 35 highlights

A display name of the form unix:0.0 will force the use of Unix Domain Sockets (UDS), which is identical to the local transport used before HP-UX 10.20. A display name of the form nn.nn.nn.nn:0.0 (where nn.nn.nn.nn is an IP address) will force the use of Internet Sockets, which is the remote transport normally used, and which can be used locally. (This will be slow.) It is possible that an application which violates the X interface standard will run correctly using UDS, but hang or coredump when using SMT. Users encountering this problem can use: DISPLAY=unix:0 to run the application compatibly, but without the performance improvement of SMT Note: If neither SMT nor UDS are desired, setting XFORCE_INTERNET=True before starting the X server forces all protocol to interact directly with the hardware internet card Performance Tuning of SMT The default values of some buffer sizes have been tuned for optimal performance in most situations. However, these are not necessarily optimal in all conditions. Under some circumstances system performance might be optimized (possibly at the expense of X performance) by tuning these parameters. Under most circumstances this should be unnecessary. The Server accepts these parameters via the X*screens file, in the ServerOptions section. In this case, the default for all SMT connections is set. Such a specification in the X*screens file might appear as: ServerOptions SMTSizes 100000,90000,90000 The client accepts these parameters via the environment variable X_SMT_SIZES. For the client, the value affects all client connections to the server made while this environment variable is set. Page 35 Graphics Administration Guide for HP-UX 10.20

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
A display name of the form
unix:0.0
will force the use of Unix Domain Sockets (UDS), which is
identical to the local transport used before HP-UX 10.20. A display name of the form
nn.nn.nn.nn:0.0
(where nn.nn.nn.nn is an IP address) will force the use of Internet Sockets, which is the remote transport
normally used, and which can be used locally. (This will be slow.)
It is possible that an application which violates the X interface standard will run correctly using UDS,
but hang or coredump when using SMT. Users encountering this problem can use:
DISPLAY=unix:0 <command_and_args>
to run the application compatibly, but without the performance improvement of SMT.
____________________________________________________________________________________
Note:
If neither SMT nor UDS are desired, setting
XFORCE_INTERNET=True
before starting the X
server forces all protocol to interact directly with the hardware internet card.
____________________________________________________________________________________
Performance Tuning of SMT
The default values of some buffer sizes have been tuned for optimal performance in most situations.
However, these are not necessarily optimal in all conditions. Under some circumstances system
performance might be optimized (possibly at the expense of X performance) by tuning these parameters.
Under most circumstances this should be unnecessary.
The Server accepts these parameters via the X*screens file, in the ServerOptions section. In this case,
the default for all SMT connections is set. Such a specification in the X*screens file might appear as:
ServerOptions
SMTSizes 100000,90000,90000
The client accepts these parameters via the environment variable X_SMT_SIZES. For the client, the
value affects all client connections to the server made while this environment variable is set.
Graphics Administration Guide for HP-UX 10.20
Page 35