Autodesk 15606-011408-9330 User Guide - Page 56

Using Multiple Servers, Understanding Multiple Simultaneous Server Requests

Page 56 highlights

Using Multiple Servers Autodesk MapGuide Server is scalable, meaning that it has mechanisms built in to take advantage of multiple servers, which improves performance. Autodesk MapGuide Server can process multiple requests simultaneously, balance the load of requests across the available servers, and use data that is distributed across different servers. This section discusses how Autodesk MapGuide Server takes advantage of multiple servers and helps you determine which is the best strategy for you. Understanding Multiple Simultaneous Server Requests Autodesk MapGuide Server is a multi-threaded application, meaning that it can process multiple requests for data in parallel, as opposed to serially processing each request one after another. MapGuide clients can send multiple simultaneous requests to several MapAgents at once and simultaneously receive the responses from those requests. This means that instead of using one server to process a large request, or sending smaller requests one at a time, multiple servers can process all smaller requests at the same time. You do this by setting up your map layers to use data from different Autodesk MapGuide Servers. Autodesk MapGuide Viewer will then send off requests for data for all of those layers in parallel, where they are all processed at the same time. Therefore, if you have three servers, processing time could be up to three times faster than using one server. For example, in the following illustration, there are requests coming from layers 1 through 6. In this example, layers 1 and 3 make the requests to server A, layers 2 and 4 send the requests to server B, and layers 5 and 6 send the requests to server C. All the requests to these servers go out at the same time, so the servers process the requests simultaneously. Each server then sends its processed data back to the Autodesk MapGuide Viewer. The Autodesk MapGuide Viewer always draws layer 1 first, and then draws all of the other layers simultaneously once it has received all of the data. 56 | Chapter 3 Designing Your System

  • 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
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204

56
|
Chapter 3
Designing Your System
Using Multiple Servers
Autodesk MapGuide Server is scalable, meaning that it has mechanisms built
in to take advantage of multiple servers, which improves performance.
Autodesk MapGuide Server can process multiple requests simultaneously,
balance the load of requests across the available servers, and use data that is
distributed across different servers. This section discusses how Autodesk
MapGuide Server takes advantage of multiple servers and helps you deter-
mine which is the best strategy for you.
Understanding Multiple Simultaneous Server Requests
Autodesk MapGuide Server is a multi-threaded application, meaning that it
can process multiple requests for data in parallel, as opposed to serially
processing each request one after another.
MapGuide clients can send multiple simultaneous requests to several
MapAgents at once and simultaneously receive the responses from those
requests. This means that instead of using one server to process a large
request, or sending smaller requests one at a time, multiple servers can
process all smaller requests at the same time. You do this by setting up your
map layers to use data from different Autodesk MapGuide Servers. Autodesk
MapGuide Viewer will then send off requests for data for all of those layers
in parallel, where they are all processed at the same time. Therefore, if you
have three servers, processing time could be up to three times faster than
using one server.
For example, in the following illustration, there are requests coming from
layers 1 through 6. In this example, layers 1 and 3 make the requests to server
A, layers 2 and 4 send the requests to server B, and layers 5 and 6 send the
requests to server C. All the requests to these servers go out at the same time,
so the servers process the requests simultaneously. Each server then sends its
processed data back to the Autodesk MapGuide Viewer. The Autodesk
MapGuide Viewer always draws layer 1 first, and then draws all of the other
layers simultaneously once it has received all of the data.