Forum: Wordfast support
Topic: Frustrated with how slow Wordfast Pro can be
Poster: ronsmith
Post title: I tried again!
Thank you SEA-words. I ended up killing the application and thankfully I had no problem. By the way, I didn't have 77k "file" loaded into WF at the time. It was a 77k "project", split in 11 files.
For the project I will start working Monday, I really would like to be able to use the Microsoft Term Collection TBX glossaries. So I decided to try to load it today into WF Pro and give it all the time it may need. The particular tbx glossary I am trying to load has 11 Mb and a total of 20,043 terms.
If you are reading this, try to think what you consider to be absurdly slow to load a glossary. What is a really absurd amount of time? I would say that anything more than a few minutes is already absurd (remember, I am on an i7 3.4 MHz with 8 Gb of RAM). If it took half an hour, I would say that it's already way beyond absurd.
I will kill WF in a moment because I need to use it for something else right now, but it's still running. I just wished it was running faster :-) . The application is loading (or trying to load) my tbx glossary for over 16h and 20min. Yes, I will spell it out: sixteen hours and twenty minutes. And it still doesn't seem to be anywhere near finishing. I wouldn't know anyway: there is no progress bar, no indication on the status bar and no console output. Nothing! It's there doing its thing, but it won't tell me what thing that is. It most probably crashed "inside": it didn't "freeze"; it still looks like it's running.
It's a shame because if I want to use any serious glossary other than the one I made while translating something, I will just have to use another CAT because WordFast Pro is useless without my glossaries.
I am using the latest version available today. I hope they fix it
Wordfast
Version: 3.2.1
Build id: [phone removed]
Topic: Frustrated with how slow Wordfast Pro can be
Poster: ronsmith
Post title: I tried again!
Thank you SEA-words. I ended up killing the application and thankfully I had no problem. By the way, I didn't have 77k "file" loaded into WF at the time. It was a 77k "project", split in 11 files.
For the project I will start working Monday, I really would like to be able to use the Microsoft Term Collection TBX glossaries. So I decided to try to load it today into WF Pro and give it all the time it may need. The particular tbx glossary I am trying to load has 11 Mb and a total of 20,043 terms.
If you are reading this, try to think what you consider to be absurdly slow to load a glossary. What is a really absurd amount of time? I would say that anything more than a few minutes is already absurd (remember, I am on an i7 3.4 MHz with 8 Gb of RAM). If it took half an hour, I would say that it's already way beyond absurd.
I will kill WF in a moment because I need to use it for something else right now, but it's still running. I just wished it was running faster :-) . The application is loading (or trying to load) my tbx glossary for over 16h and 20min. Yes, I will spell it out: sixteen hours and twenty minutes. And it still doesn't seem to be anywhere near finishing. I wouldn't know anyway: there is no progress bar, no indication on the status bar and no console output. Nothing! It's there doing its thing, but it won't tell me what thing that is. It most probably crashed "inside": it didn't "freeze"; it still looks like it's running.
It's a shame because if I want to use any serious glossary other than the one I made while translating something, I will just have to use another CAT because WordFast Pro is useless without my glossaries.
I am using the latest version available today. I hope they fix it
Wordfast
Version: 3.2.1
Build id: [phone removed]