This shows you the differences between two versions of the page.
rhino:citrix [2016/02/25] |
rhino:citrix [2020/08/14] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Does Rhino work on CITRIX servers? ====== | ||
+ | |||
+ | ======Caveat====== | ||
+ | We have no actual experience running Rhino on CITRIX, but based on our own thought experiments, | ||
+ | |||
+ | ======Overview====== | ||
+ | There are at least two ways to configure Rhino on CITRIX: | ||
+ | |||
+ | - Use CITRIX to deploy Rhino to the client computer. | ||
+ | - Run Rhino on the CITRIX server and stream the UI to the client. | ||
+ | |||
+ | ======1. Use CITRIX to deploy Rhino====== | ||
+ | Rhino 4.0 uses Windows Installer for deployment, and there are scripted installation instructions available at: [[rhino: | ||
+ | |||
+ | It is your responsibility to assure that your organization owns enough licenses as the number of Rhinos running simultaneously. It is your responsiblity to monitor usage and deny usage to your clients if you have reached your license count. | ||
+ | |||
+ | ======2. Run Rhino on the CITRIX server and stream the UI====== | ||
+ | We recommend that you do not run Rhino on a CITRIX server. It is possible to install and run Rhino on a CITRIX server, but it is not likely that the user experience will be a positive one. | ||
+ | |||
+ | Before investing in a CITRIX solution for Rhino, we recommend that you download the Rhino Evaluation and try it - be sure to have many clients actively running Rhino simultaneously before you determine whether it really works. | ||
+ | |||
+ | **Graphics Performance** | ||
+ | |||
+ | Rhino is graphics intensive. Unlike many text-based products (such as e-mail, word processing, and spreadsheets), | ||
+ | |||
+ | This assumes that the server is capable of generating images that quickly. To have 30 clients each generating that kind of frame rate requires some substantial hardware acceleration - you'll likely need a dedicated GPU (graphics processor) for each client. | ||
+ | |||
+ | If you can't reliably get this kind of network traffic and graphics performance (when all 30 clients are using Rhino) you'll likely get a ton of complaints. | ||
+ | |||
+ | **CPU Overhead** | ||
+ | |||
+ | Rhino has several features that are CPU intensive. It is not uncommon for a user to spike CPU usage to 100% for between 3 seconds and 3 minutes, depending on the complexity of the operation. Rhino doesn' | ||
+ | |||
+ | **RAM Availability** | ||
+ | |||
+ | Your clients will likely use as much RAM as they can. When people have a lot of processor and RAM available, they tend to use it. Rhino 3.0 will only use 2GB, but Rhino 4.0 can use 3GB. I have no idea how big the models are that your clients will be making, but it's not uncommon for people to start using 500MB - 1.5GB. | ||
+ | |||
+ | **Your Experience** | ||
+ | |||
+ | If you have tried Rhino on CITRIX, please edit this wiki page and tell us about it. | ||
+ | |||
+ | ======Actual User Experiences====== | ||
+ | |||
+ | **Licensing Problems** | ||
+ | |||
+ | It is more likely that you'll run into license problems before you reach any performance limit. RhinoLM only allows one user at once to get a licence (in either Standalone or Workgroup/ | ||
+ | |||
+ | Using the Zoo license server will allow multiple concurrent Rhino users. Setting up the Zoo should get around this limit. For more information on the Zoo in this environment see [[zoo: | ||
+ | |||
+ | |||
+ | |||