Multi-server deployment
A multi-server deployment implies that you install the ETS application on one Master host or machine, while you install the ETS Language Pairs on several Worker hosts.
ETS multi-server deployment is designed for moderate to high translation volumes. For example, a multi-server deployment can support multiple users translating approximately 100 million words per day, using multiple MT language pairs.
In this multi-server deployment example, ETS is running on five machines: Bergamot, Thymes, Eucalyptus, Rosemary, and Laurel. The ETS application was installed on Bergamot as a Master host so that it can serve the Web GUI service, which provides a user-interface that is accessible via a web browser, and the REST API service, which provides industry standard HTTP methods for application integrations. Since the usage scenario aims to serve a large pool of simultaneous users, Bergamot is dedicated to hosting the Web GUI and the REST API only, and therefore no ETS language pairs are installed on Bergamot.
Having six Job Engines across four different hosts provide this ETS instance with redundancy and higher capacity for source language detection if the source language is set to auto-detect, for segmentation of the source input, and for the compilation of the translation into the desired output format. Thymes and Rosemary have more memory, so they can support more Translation Engines, which are more memory intensive services. There are twice as many Translation Engines for each of French to English and Spanish to English language pairs than there are for the others, because those languages are expected to have higher usages.
The following are the high level steps taken during the four parts of the deployment process to achieve this ETS cluster setup:
Part 1: Installing the ETS application
The ETS application is installed as a Master host on Bergamot, while it was installed as a Worker host on Thymes, Eucalyptus, Rosemary, and Laurel.
Part 2: Installing the ETS language pairs
The ETS language pairs were installed on the host machines that will run Translation Engines for those specific language pairs. Specifically, Arabic, Russian, Bengali, Italian, and Japanese to English were installed onThymes and Rosemary. French and Spanish to English were installed onEucalyptus and Laurel.
Part 3: Obtaining the ETS licenses
For Thymes and Rosemary, the myhosts.json files were sent to SDL licensing, with a request for five language pairs (Arabic to English, Russian to English, Bengali to English, Italian to English, and Japanese to English). For Eucalyptus and Laurel, their myhosts.json files were sent to SDL licensing with a request for two language pairs (French to English and Spanish to English). The maximum Processing Units that each language pair can use can be optionally requested, but most likely unnecessary, as they are specified by the purchase order contract.
- Add Thymes, Eucalyptus, Rosemary, and Laurel as hosts.
- Add Job Engines and Translation Engines to each host as the diagram shows. Thymes and Rosemary have the same Job Engines and Translation Engines setup. Eucalyptus and Laurel have the same Job Engines and Translation Engines setup.