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

normal, small X messages. Large messages can still be sent at high efficiency. In a memory-poor

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 36 highlights

In either case, the format and meaning of the fields is the same: [, [, ]] with no embedded blanks, e.g. 32000,16000,5000 32000 0 Although the default is "SMTSizes 0,0,0," a specification of "SMTSizes 100000,90000,90000" is optimal in most situations if SMT is desired. The values are accepted as positive decimal, hex, or octal values according to the C conventions. The special value of 0 (for buffer size; all other values are ignored) indicates that SMT is to be suppressed. controls the amount of shared memory allocated for the transport (in bytes). This has the largest effect on system performance. The value is rounded up to the next page boundary. Larger values yield faster X performance, but there is a point of diminishing returns. The default is 100000 (which is rounded to 0x19000) except for a diskless Xserver which has a default of 0. is a soft boundary which affects the load on the Virtual Memory system. The value is rounded up to the next page boundary. The smaller the value, the smaller the number of pages actually used while sending "normal, small" X messages. Large messages can still be sent at high efficiency. In a memory-poor system making this small may be an advantage, but if sufficient memory is available, make the value the same as the High Water size (if the option is used). (Space is left for a control region if necessary.) The value must fit within the region (and should be smaller), the buffer must fit within the high-water mark (and consequently the buffer must fit within the whole region). If these parameters are used, be sure to confirm that they actually cause an improvement in actual usage situations. Incorrect values can degrade performance. Page 36 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
In either case, the format and meaning of the fields is the same:
<region_size>
[,
<high_water>
[,
<buffer_size>
]] with no embedded blanks, e.g.
32000,16000,5000
32000
0
Although the default is "
SMTSizes 0,0,0,
" a specification of "
SMTSizes 100000,90000,90000
" is optimal
in most situations if SMT is desired.
The values are accepted as positive decimal, hex, or octal values according to the C conventions.
The special value of 0 (for buffer size; all other values are ignored) indicates that SMT is to be
suppressed.
<region_size>
controls the amount of shared memory allocated for the transport (in bytes). This has the largest effect
on system performance. The value is rounded up to the next page boundary. Larger values yield faster X
performance, but there is a point of diminishing returns. The default is 100000 (which is rounded to
0x19000) except for a diskless Xserver which has a default of 0.
<high_water>
is a soft boundary which affects the load on the Virtual Memory system. The value is rounded up to the
next page boundary. The smaller the value, the smaller the number of pages actually used while sending
"normal, small" X messages. Large messages can still be sent at high efficiency. In a memory-poor
system making this small may be an advantage, but if sufficient memory is available, make the value the
same as the High Water size (if the option is used). (Space is left for a control region if necessary.)
The
<high_water>
value must fit within the region (and should be smaller), the buffer must fit within
the high-water mark (and consequently the buffer must fit within the whole region).
If these parameters are used, be sure to confirm that they actually cause an improvement in actual usage
situations. Incorrect values can degrade performance.
Graphics Administration Guide for HP-UX 10.20
Page 36