Exceed onDemand A Technical Whitepaper
Exceed onDemand A Technical Whitepaper Exceed onDemand A Technical Whitepaper
Exceed onDemand 5 — A Technical Whitepaper Resume a Session Exceed on Demand Exceed on Demand Client X Proxy Manager Proxy Cluster Manager Join a Session 20 Request: Get suspended sessions Reply: Return List Request: Select Session Reply: Return Authentication Token Request: Resume Reply: Return Proxy Port, Display Number and Parameters Event: Connect Event: Session Resumed Exceed on Demand Exceed on Demand Client X Proxy Manager Proxy Cluster Manager Request: Get Shared Sessions Reply: Return List Request: Select Session Reply: Return Authentication Token Request: Share Reply: Return Proxy Port, Display Number and Parameters Event: Connect Event: Session Joined
Server Requirements Exceed onDemand Resource Usage > Exceed onDemand 5 — A Technical Whitepaper “What kind of server do I need for Exceed onDemand Server?” This is a valid and logical question to ask when considering adopting Exceed onDemand--it is also a very difficult question to answer. It is akin to asking what machine is needed to run Windows XP. The answer to both questions is that it depends largely on how and for what the product will be used. If the machine only needs to run Exceed onDemand in passive mode and launch simple X applications, then most decent machines in the market will do. But this is rarely how Exceed onDemand is used. After all, Exceed onDemand is a PC X Server and a graphical emulator. The access of the host resources can be broken down into three stages: Stage 1 — A fixed amount of resources are used to launch Exceed onDemand. Stage 2 — As an emulator, Exceed onDemand incurs additional resources for every X application it handles. Stage 3 — If the X application is running on the same host as the Server, then the application itself will consume resources. So, to rephrase the original question: a) What kind of X applications will my users access? b) Will the X applications and Exceed onDemand Server run on the same machine? c) How many users will access each X application? d) What is the usage pattern likely to be? Is there a peak hour when everyone will log on to the Server at the same time, or will the usage be evenly spread out throughout the day? So knowing the size of the deployment and its intended usage is essential. A site deploying Exceed onDemand to 100 users, each running a copy of xterm, will have different server requirements than another site that deploys Exceed onDemand to 100 users with each running an instance of a complicated 3D imaging software product. However, this document will try to provide some basic guidelines and examples of system resource usage and bandwidth consumption when Exceed onDemand runs some common X applications. Users can use this information as a reference when deciding the size and capacity of a server intended to house Exceed onDemand Server, but they are strongly advised to collect data that is unique to their environment. 21
- Page 1: Transforming Information into Intel
- Page 4 and 5: Exceed onDemand 5 — A Technical W
- Page 6 and 7: Exceed onDemand 5 — A Technical W
- Page 8 and 9: Exceed onDemand 5 — A Technical W
- Page 10 and 11: Exceed onDemand 5 — A Technical W
- Page 12 and 13: Exceed onDemand 5 — A Technical W
- Page 14 and 15: Exceed onDemand 5 — A Technical W
- Page 16 and 17: Exceed onDemand 5 — A Technical W
- Page 18 and 19: Exceed onDemand 5 — A Technical W
- Page 22 and 23: Exceed onDemand 5 — A Technical W
- Page 24 and 25: Exceed onDemand 5 — A Technical W
- Page 26 and 27: Exceed onDemand 5 — A Technical W
- Page 28 and 29: Exceed onDemand 5 — A Technical W
- Page 30 and 31: Exceed onDemand 5 — A Technical W
- Page 32 and 33: Exceed onDemand 5 — A Technical W
- Page 34 and 35: Exceed onDemand 5 — A Technical W
- Page 36 and 37: Exceed onDemand 5 — A Technical W
- Page 38 and 39: Exceed onDemand 5 — A Technical W
- Page 40 and 41: Exceed onDemand 5 — A Technical W
- Page 42 and 43: Exceed onDemand 5 — A Technical W
- Page 44 and 45: Exceed onDemand 5 — A Technical W
- Page 46 and 47: Exceed onDemand 5 — A Technical W
- Page 48 and 49: Exceed onDemand 5 — A Technical W
- Page 50 and 51: Exceed onDemand 5 — A Technical W
- Page 52 and 53: Exceed onDemand 5 — A Technical W
- Page 54 and 55: Exceed onDemand 5 — A Technical W
- Page 56 and 57: Exceed onDemand 5 — A Technical W
- Page 58 and 59: Exceed onDemand 5 — A Technical W
- Page 60 and 61: Exceed onDemand 5 — A Technical W
- Page 62: Server > Desktop Consolidation > X
Server Requirements<br />
<strong>Exceed</strong> <strong>onDemand</strong> Resource Usage<br />
> <strong>Exceed</strong> <strong>onDemand</strong> 5 — A <strong>Technical</strong> <strong>Whitepaper</strong><br />
“What kind of server do I need for <strong>Exceed</strong> <strong>onDemand</strong> Server?” This is a valid and logical question to<br />
ask when considering adopting <strong>Exceed</strong> <strong>onDemand</strong>--it is also a very difficult question to answer. It is<br />
akin to asking what machine is needed to run Windows XP. The answer to both questions is that it<br />
depends largely on how and for what the product will be used.<br />
If the machine only needs to run <strong>Exceed</strong> <strong>onDemand</strong> in passive mode and launch simple X<br />
applications, then most decent machines in the market will do. But this is rarely how <strong>Exceed</strong><br />
<strong>onDemand</strong> is used. After all, <strong>Exceed</strong> <strong>onDemand</strong> is a PC X Server and a graphical emulator.<br />
The access of the host resources can be broken down into three stages:<br />
Stage 1 — A fixed amount of resources are used to launch <strong>Exceed</strong> <strong>onDemand</strong>.<br />
Stage 2 — As an emulator, <strong>Exceed</strong> <strong>onDemand</strong> incurs additional resources for every X application<br />
it handles.<br />
Stage 3 — If the X application is running on the same host as the Server, then the application itself<br />
will consume resources.<br />
So, to rephrase the original question:<br />
a) What kind of X applications will my users access?<br />
b) Will the X applications and <strong>Exceed</strong> <strong>onDemand</strong> Server run on the same machine?<br />
c) How many users will access each X application?<br />
d) What is the usage pattern likely to be? Is there a peak hour when everyone will log on to the Server<br />
at the same time, or will the usage be evenly spread out throughout the day?<br />
So knowing the size of the deployment and its intended usage is essential. A site deploying <strong>Exceed</strong><br />
<strong>onDemand</strong> to 100 users, each running a copy of xterm, will have different server requirements<br />
than another site that deploys <strong>Exceed</strong> <strong>onDemand</strong> to 100 users with each running an instance of<br />
a complicated 3D imaging software product.<br />
However, this document will try to provide some basic guidelines and examples of system resource<br />
usage and bandwidth consumption when <strong>Exceed</strong> <strong>onDemand</strong> runs some common X applications.<br />
Users can use this information as a reference when deciding the size and capacity of a server<br />
intended to house <strong>Exceed</strong> <strong>onDemand</strong> Server, but they are strongly advised to collect data that<br />
is unique to their environment.<br />
21