Large Files in Wordfast Pro Auteur du fil: JohnWhi
|
|---|
JohnWhi
Royaume-Uni
Local time: 20:50
français vers anglais
I am using Wordfast Pro 9.9.1 mainly on the M1 Macbook Air with 16Gb memory, also on the Intel iMac with 40Gb memory. A client has asked for a quote on a long document, 567794 words over 1563 pages, that they have spit into four parts, varying between 64258 and 293756 words. I converted from PDF to Word using Adobe PDF Export then ran the TransTools+ Pre-flight Checker before loading the files to WFP. Although the project opens in a couple of seconds, I timed the largest file as typically taking... See more I am using Wordfast Pro 9.9.1 mainly on the M1 Macbook Air with 16Gb memory, also on the Intel iMac with 40Gb memory. A client has asked for a quote on a long document, 567794 words over 1563 pages, that they have spit into four parts, varying between 64258 and 293756 words. I converted from PDF to Word using Adobe PDF Export then ran the TransTools+ Pre-flight Checker before loading the files to WFP. Although the project opens in a couple of seconds, I timed the largest file as typically taking 10 minutes 40 seconds to open. Once open, everything (moving from segment to segment, retrieving information from the TM) works as quickly and as smoothly as usual. My question is whether the extended time taken to open means the file is simply too large. Is there an optimal maximum size? I could easily split the large files, and my output is not going to be in Word documents, (I usually use a PDF editor to paste translated text into the original document, maintaining format and graphics), so the output format is irrelevant. ▲ Collapse
| | | | Philippe Locquet 
Portugal
Local time: 20:50
Membre (2013)
anglais vers français
+ ...
JohnWhi wrote:
I am using Wordfast Pro 9.9.1 mainly on the M1 Macbook Air with 16Gb memory, also on the Intel iMac with 40Gb memory. A client has asked for a quote on a long document, 567794 words over 1563 pages, that they have spit into four parts, varying between 64258 and 293756 words. I converted from PDF to Word using Adobe PDF Export then ran the TransTools+ Pre-flight Checker before loading the files to WFP. Although the project opens in a couple of seconds, I timed the largest file as typically taking 10 minutes 40 seconds to open. Once open, everything (moving from segment to segment, retrieving information from the TM) works as quickly and as smoothly as usual. My question is whether the extended time taken to open means the file is simply too large. Is there an optimal maximum size? I could easily split the large files, and my output is not going to be in Word documents, (I usually use a PDF editor to paste translated text into the original document, maintaining format and graphics), so the output format is irrelevant.
Hi, in my experience, what matters most is the weight of the original file. You are doing the right: waiting and letting the program do its thing. Once that's over, things should be back to snappy. You'll have to wait on export too when you get your translated file.
Mac chips are good but Apple has you pay through the nose to get a higher amount of RAM. To treat big files like this you'd want ideally 32 GB of RAM and at least a 6 cores processor.
On Windows, I've seen 6GB source files be processed very fast but the RAM usage for that was around 11GB, so you see how 16 can seem small.
What can help is for you to close everything else on your PC, no minimized, closed. You can also temporarily turn off the Wi-Fi in the Finder settings, this will allow more RAM and CPU to be available for the process.
If you have a colleague with a 32GB RAM (or more) computer and Wordfast Pro, you can ask them to process the file for you so that they send you the txlf for you to work on and they can do the export later. But for 10 minutes or less, grabbing a cup of tea seems reasonable.
Hope this helped a little
| | | | JohnWhi
Royaume-Uni
Local time: 20:50
français vers anglais
AUTEUR DU FIL
Thanks for the suggestion, Philippe. In effect, you are saying that, if I load the file on the Intel iMac with 40GB memory, then transfer the txml files to the M1 MacBook, they will open more quickly. I am not sure it is a memory issue, and the iMac is still opening the file after 16 minutes. With the file opening on both machines, I have been monitoring 'memory pressure' in Activity Monitor. Memory used for Wordfast is 1.45GB on the iMac, 1.41GB on the MacBook. Total memory used is 9.45GB on th... See more Thanks for the suggestion, Philippe. In effect, you are saying that, if I load the file on the Intel iMac with 40GB memory, then transfer the txml files to the M1 MacBook, they will open more quickly. I am not sure it is a memory issue, and the iMac is still opening the file after 16 minutes. With the file opening on both machines, I have been monitoring 'memory pressure' in Activity Monitor. Memory used for Wordfast is 1.45GB on the iMac, 1.41GB on the MacBook. Total memory used is 9.45GB on the iMac and 9.74GB on the MacBook, where a browser is also open to write this. As you say, total file size does make a difference, and I suspect some splitting is called for if I am given the go-ahead for this. ▲ Collapse
| | | | JohnWhi
Royaume-Uni
Local time: 20:50
français vers anglais
AUTEUR DU FIL | Smaller files no problem | Jan 15 |
Just reporting back, having split the largest file into four, 108 to 110 pages, varying between 53718 and 103617 words. The largest opens in 50 seconds, the smallest in 18 seconds. That will make life easier. The second largest file, 127700 words over 542 pages, opens in about a minute, so no need for further splits.
| | |
|
|
|
Philippe Locquet
Portugal
Local time: 20:50
Membre (2013)
anglais vers français
+ ...
JohnWhi wrote:
Thanks for the suggestion, Philippe. In effect, you are saying that, if I load the file on the Intel iMac with 40GB memory, then transfer the txml files to the M1 MacBook, they will open more quickly. I am not sure it is a memory issue, and the iMac is still opening the file after 16 minutes. With the file opening on both machines, I have been monitoring 'memory pressure' in Activity Monitor. Memory used for Wordfast is 1.45GB on the iMac, 1.41GB on the MacBook. Total memory used is 9.45GB on the iMac and 9.74GB on the MacBook, where a browser is also open to write this. As you say, total file size does make a difference, and I suspect some splitting is called for if I am given the go-ahead for this.
I'm not sure which CPU the iMac has, but that's worth a try yes. You can just move around the GLP package.
Splitting works too. If you're familiar with the chain files and similar features, your experience will be good.
You can open all your splits at the same time and "chain" them together into one long txlf (does not modify the txlf, just the Ui), which means, segment filters work. Or if you work on one and leave the other ones opened, depending on your settings, you can have all files (Auto propagation).
just some quick tips!
My bests
[Edited at 2025-01-16 08:48 GMT]
| | | | JohnWhi
Royaume-Uni
Local time: 20:50
français vers anglais
AUTEUR DU FIL | Many thanks for suggestions | Jan 16 |
Many thanks for the suggestions, Philippe. I have taken a note in case I ever need to output a long Word file. I agree the old-style Intel Quad-Core i5 processor was probably the reason for the slower performance on the iMac. As it happens, the quick and easy solution was to split up the long PDF (various tools will do this at the press of a few buttons), convert to Word and preflight check, then set up a sub-project. Having an output of four files is no problem, as my usual practice is to paste... See more Many thanks for the suggestions, Philippe. I have taken a note in case I ever need to output a long Word file. I agree the old-style Intel Quad-Core i5 processor was probably the reason for the slower performance on the iMac. As it happens, the quick and easy solution was to split up the long PDF (various tools will do this at the press of a few buttons), convert to Word and preflight check, then set up a sub-project. Having an output of four files is no problem, as my usual practice is to paste the translated content therein into the original PDF source file using my PDF editor. ▲ Collapse
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Large Files in Wordfast Pro | Trados Business Manager Lite | Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.
More info » |
| | Trados Studio 2022 Freelance | The leading translation software used by over 270,000 translators.
Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop
and cloud solution, empowering you to work in the most efficient and cost-effective way.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news related to Wordfast
