HP ProLiant xw2x220c Remote Graphics Software 5.3.0 User Guide - Page 149

Image update request #1

Page 149 highlights

The sequence chart in Figure 8-6 shows operation for the default property value of 4. In this case, the Receiver can have up to 4 image update requests outstanding at any given time. When image update response #1 is received (meaning that there are now 3 outstanding image update requests), the Receiver can issue image update request #5 (again, up to a maximum of 4 outstanding image update requests at any given time). Figure 8-6 Sequence chart for the default property value of 4 Sender Receiver Image update request #1 Image update request #2 Image update request #3 Image update request #4 Image update response #1 Image update request #5 Image update response #2 Image update request #6 The sequence can vary considerably from that shown in Figure 8-6. For example, image update response #1 might be received prior to issuance of image update request #4. Also, TCP will temporarily block the Sender from sending further data if the Receiver network buffer becomes full. Nonetheless, the sequence shown in Figure 8-6 serves to parallelize local display updates that otherwise would occur serially. The default property value of 4 was determined empirically as a good compromise for both low and high-latency network environments. Larger numbers of outstanding requests may be beneficial in some cases depending on the number and types of updates occurring. In high-latency network environments, HP recommends that you characterize RGS performance for different values of the Rgreceiver.MaxImageUpdateRequests property. RGS properties 149

  • 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
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196

RGS properties 149
The sequence chart in Figure 8-6 shows operation for the default property value of 4. In this case, the Receiver
can have up to 4 image update requests outstanding at any given time. When image update response #1 is
received (meaning that there are now 3 outstanding image update requests), the Receiver can issue image update
request #5 (again, up to a maximum of 4 outstanding image update requests at any given time).
Figure 8-6
Sequence chart for the default property value of 4
The sequence can vary considerably from that shown in Figure 8-6. For example, image update response #1
might be received prior to issuance of image update request #4. Also, TCP will temporarily block the Sender from
sending further data if the Receiver network buffer becomes full. Nonetheless, the sequence shown in Figure 8-6
serves to parallelize local display updates that otherwise would occur serially.
The default property value of 4 was determined empirically as a good compromise for both low and high-latency
network environments. Larger numbers of outstanding requests may be beneficial in some cases depending on the
number and types of updates occurring.
In high-latency network environments, HP recommends that you
characterize RGS performance for different values of the
Rgreceiver.MaxImageUpdateRequests
property.
Sender
Receiver
Image update request #1
Image update request #2
Image update response #1
Image update request #3
Image update request #4
Image update request #5
Image update response #2
Image update request #6