WorldServer - what is Cache TM and how is it used?
000015868 |5/7/2021 11:25 AM
Scope/Environment
WorldServer 11.6.1 and later
Question
I have heard about Cache TM but I am not sure how these new feature works. Can you explain? |
Answer
In earlier versions of WorldServer, the segmentation and pre-translation processes would take up to half of the time required for the entire workflow to be processed, especially in the case of large projects and complex workflows. This was mostly due to the fact that each TM lookup retrieved data directly from the database, which slowed down the translation process considerably, especially when dealing with large TMs. Starting with WorldServer 11.6, however, a caching mechanism has been implemented to drastically improve TM lookup times. Thus, for each project, TM leverage is saved in a cached .tmx file and WorldServer now uses this .tmx file instead of the database to retrieve data when performing lookups:
- Immediately after the project assets are segmented, a background job starts to run and saves the TM leverage calculated during the Segment Asset step in a .tmx file. One .tmx file is created for each project.
- The TM leverage calculated during the Segment Asset step is saved in a cached .tmx file. You can download this file from WorldServer Explorer at any time. The .tmx file is saved in the Target language subfolder of the project directory. For example, /FileSystem/CLIENT/Projects/3491_test_project/Target-German (Germany)/Project-TM. You can see this additional folder in WorldServer Explorer. Here is an example:
- If the project type uses a TM sequence instead of a TM, all the TMs included in that TM sequence are cached. In this case, one .tmx file is created for each language and for each TM within the TM sequence. Example:
- The caching mechanism does not apply to projects segmented with legacy filters (old Idiom filters). Although you will still see the Project-TM folder if you enable Cached TM at the Segment Asset step while using Legacy filters, the cached TMX file will contain no TM entries. Additionally, there will be an error when exporting the asset to a WSXZ package, resulting in an unsuccessful export.
- When you export a translation kit from the Tasks page and select WSXZ as the export format, the .tmx file created during segmentation is added to the translation kit if you select the option Use cached Project TM (which is the default one) or Use cached Project TM and include Link. The advantage is that exporting becomes faster because WorldServer does not need to search the TM again for relevant matches. It will use the existing TMX file(s) created during segmentation and will add it/them to the WSXZ package.
- Possible disadvantage: If your project/task is exported a significant time after segmentation, your Translation Memory (TM) may have been updated with relevant entries in the meantime. If you are concerned about not exporting these relevant TM entries added after segmentation, you should use the "classic" method to export your package by selecting Create Project TM. The Generate Translation Kit Automatic Action has been marked as deprecated and has been replaced with an automatic action called Create Project Package, which also features the new caching mechanism. This article is about the Create Project Package Automatic step. |
Reference