Forum: MemoQ support
Topic: MemoQ 2014 R2 very, very slow!?!
Poster: Siegfried Armbruster
Post title: MemoQ might have same space for improvement
[quote]Dominique Pivard wrote:
What you could do is split your TMX into four parts and import them separately. In fact, a quarter of your DGT TM may be quite sufficient for the purpose of creating a Muse. Sometimes more isn't better. [/quote]
I managed to import the TMX, it only took 33 hours :-(. MemoQ only used 10-20 % of my processor but up to 94% of my 8 GB of memory. The computer more or less froze just handling this import.
I already deleted 1 million duplicate entries from the DGT before I started to import it. I don't see the reason why I should only use 1/4th of the available data and why this should give me the same results? Has anybody reliable data on this?
Funny enough, SDL Studio has no problem handling this amount of data, and is much faster (at least 5 times) processing it. It uses a max of 50% of my processor about 40% of the memory and allowed me to run several other applications in parallel. As I see it, MemoQ might have some space for improvement in this area.
[Edited at 2015-07-02 10:53 GMT]
Topic: MemoQ 2014 R2 very, very slow!?!
Poster: Siegfried Armbruster
Post title: MemoQ might have same space for improvement
[quote]Dominique Pivard wrote:
What you could do is split your TMX into four parts and import them separately. In fact, a quarter of your DGT TM may be quite sufficient for the purpose of creating a Muse. Sometimes more isn't better. [/quote]
I managed to import the TMX, it only took 33 hours :-(. MemoQ only used 10-20 % of my processor but up to 94% of my 8 GB of memory. The computer more or less froze just handling this import.
I already deleted 1 million duplicate entries from the DGT before I started to import it. I don't see the reason why I should only use 1/4th of the available data and why this should give me the same results? Has anybody reliable data on this?
Funny enough, SDL Studio has no problem handling this amount of data, and is much faster (at least 5 times) processing it. It uses a max of 50% of my processor about 40% of the memory and allowed me to run several other applications in parallel. As I see it, MemoQ might have some space for improvement in this area.
[Edited at 2015-07-02 10:53 GMT]