另外,您使用的是 Windows 還是 Linux,@anon692560?
我使用 Linux 版本的 Paratext 已經有一段時間了。我很欣賞能在「foss」(自由及開放原始碼軟體)環境中運行它的功能。我使用的是 Wasta 20.04(幾週前剛安裝的新系統),Paratext 最近更新到了 9.0.100.10256。當 Wasta 提示時,我會套用系統和安全更新,所以我想我的作業系統是最新的。我有 16 GB 的 RAM,一顆 i5 @ 2.3 GHz 處理器——我的電腦處理大多數事情都相當得心應手。但 Paratext——以及很大程度上 FLEX——幾乎慢得令人難以忍受。
Paratext 大約需要兩個小時才能用掉 1.7 GB 或更多的記憶體,到那時任何任務都變得艱難——點擊某個東西後,你得等待、等待、再等待,久到開始懷疑你的點擊是否真的被註冊了;打字時也不確定自己在單字的哪個位置,或者是否犯了錯,因為文字出現需要幾秒鐘;等等。達到 2.0 GB 時,就該關閉 PT 並重新開始攀登「記憶體山」了…… [我已經養成習慣,在 PT 中工作時關閉任何我不絕對需要開啟的東西——瀏覽器、文字處理器,甚至 Logos(這其實是多餘的……)——只為了釋放記憶體。我原本以為 16 GB 中用掉 2 GB 不會成為問題。 ]
說到關閉 PT,這意味著要進入系統監視器(System Monitor)並點擊「結束程序」(End Process),因為即使 Paratext 從螢幕上消失,它仍然駐留並佔用其中一個處理器核心的 100%(總量的 25%)。有一次我讓它這樣放了好幾個小時,該程序從未自行結束…… [我已經為此提交了日誌,但我不知道結果如何。]
我曾希望升級到 Wasta 20.04 和 Paratext 9.0.100 會有幫助,但情況與我在 Wasta 18.04 和早期版本 PT 上的體驗幾乎一樣。不幸的是,這並沒有幫助。我一直在想這是否只是我的個人體驗,但我聽了幾位其他 Linux 用戶說他們的情況也是如此。現在連你也是,@anon692560…… 我想知道是否有什麼我們可以做的來改善這種情況。
And are using Windows or Linux, @anon692560?
I’ve been using the Linux version of Paratext for a while. I do appreciate the ability to run it in a “foss” environment. I’m using Wasta 20.04 (fresh install a few weeks ago), and Paratext recently updated to 9.0.100.10256. I apply system and security updates when Wasta prompts, so I think I’m up to date OS-wise. I’ve got 16 GB of RAM, an i5 @ 2.3 GHz processor–my computer handles most anything quite capably. But Paratext–and to much the same extent, FLEX–is almost unbearably slow.
It takes about two hours for Paratext to use up 1.7 GB of memory or more, at which point any task becomes a struggle–click something and wait and wait and wait long enough that you begin to wonder if your click really registered; type and not be sure where you’re at in the word or if you made a mistake because it takes a few seconds for the text to appear; and so on. At 2.0 GB, it’s time to shut PT down and start the climb up “memory mountain” all over again… [It has become my practise to shut down anything I don’t absolutely need open when I’m working in PT–browser, word processor, even Logos (which is counter-productive…)–just to free up memory. Not that I would have thought 2 GB out of 16 would be a deal breaker. ]
When it comes to shutting down PT it means going into System Monitor and clicking “End Process”, because even after Paratext disappears from the screen it stays resident and has one of the processor cores pegged at 100% (25% of total). I left it for a few hours once, and the process never ended on its own… [I have submitted logs for this, but I don’t know what ever came of that.]
I had hoped that upgrading to Wasta 20.04 and Paratext 9.0.100 would help, but it’s pretty much the same as my experience with Wasta 18.04 and earlier versions of PT. Unfortunately, it hasn’t helped. I had been wondering if this is just my experience, but I’ve heard from a few other Linux users that it’s the same for them. And now you, @anon692560… I’m interested to learn if there’s anything we can do to improve the situation.
機器翻譯自 English 顯示原文