• State Verified Answer
  • Replies 3 replies
  • Subscribers 432 subscribers
  • Views 1843 views
  • Users 0 members are here
Options
Related

Using Uplift with big TM's - Best set-up?

Toon Theuwis

I'm trying to figure out what the best setup would be to use Uplift with the large TM's I'm using for EU content. I have GB's of TM's, all grouped per subject. For each project I would typically use a couple of .sdltm files simultaneously (each being between 500-700 Mb) depending on the document I had to translate.

Now with the Uplift feature, I noticed that my TM's are being blown up to be 4 times as big. So I ended up splitting my original TM'S in 10 pieces. A 50Mb TM would then grow to be 200 MB after the Uplift upgrade, meaning I now have 2 Gb of chopped up TM's where I used to have 500Mb for 1 TM. Say that I need to use TM's from 3 or 4 subjects to translate a document. I used to be able to use 4 X 500 Mb TM's in my projects. Now I wonder if it will still work if I add 40 X 200 Mb. It just doesn't look like a good idea. I could merge the TM's a little and play around with this. The only thing is that all this is taking an awful lot of time (splitting, converting, upgrading to Uplift, merging all these GB's of TM's).

My question: From a designer point of view, what would be a good setup to start testing? I'm just afraid that Uplift might not be usable for really big TM's.

BTW: never had any performance issues before. I'm using a Macbook Pro attached to an external screen, Parallels, 8 GB Ram (4GB assigned to Windows).
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hi, Toon - can I ask why you chose to split the original TMs into 10 pieces? I appreciate that the 50MB TM would have grown to 200MB after upLIFT fragment alignment (that extra size is mainly from the extensive indexing that's meant to provide fast fragment recall) ... but I wouldn't expect there to be a particular need to split the content into smaller TMs. In general, I'd say you'd get better performance continuing to use the same number of TMs, even though the actual sdltm files are larger. (If you split the content into separate TMs, Studio has to query them separately, which can end up taking longer.) But tell me if that's not an option for you ... We have tested upLIFT on some pretty large TMs (e.g. 4.5GB after fragment alignment), so I don't think you need worry about the total size in most cases.
Reply
  • 0

    Hi, Toon - can I ask why you chose to split the original TMs into 10 pieces? I appreciate that the 50MB TM would have grown to 200MB after upLIFT fragment alignment (that extra size is mainly from the extensive indexing that's meant to provide fast fragment recall) ... but I wouldn't expect there to be a particular need to split the content into smaller TMs. In general, I'd say you'd get better performance continuing to use the same number of TMs, even though the actual sdltm files are larger. (If you split the content into separate TMs, Studio has to query them separately, which can end up taking longer.) But tell me if that's not an option for you ... We have tested upLIFT on some pretty large TMs (e.g. 4.5GB after fragment alignment), so I don't think you need worry about the total size in most cases.
Children