HFM.NET v0.9.7.558
34 views
Skip to first unread message
harlam357
Aug 30, 2016, 1:06:44 AM8/30/16
to hfm-net
I'm releasing this latest build here before pushing it to the auto-update mechanism. Please test.
HFM.NET v0.9.7.558
Download Location on Google Drive: https://drive.google.com/open?id=0B8d5F59S5sCiS1RISzdsaEd5UXM
- Change: Reworked HFM's FAH Log File Parsing API. Changes targeted to make v7 log files a first class citizen in lieu of of being a derivation of v6 logs.
As a result HFM as a client application does much less repeated parsing and scanning of the log data which results in less memory usage and faster client data processing.
I'm also curious to see how well GPU work unit failures are now captured from v7 clients. I don't have any modern GPUs so this is obviously difficult for me to test.
- Change/Fix: Replaced the preferences/configuration storage mechanism (user.config) which has been a source of random problems since HFM's inception.
Existing preferences will migrate to the new (home rolled) storage mechanism. The new preferences can be found in the HFM data files folder (config.xml).
- Fix: Crash reported by john on the hfm-net Google Group. He discovered a race condition between HFM attempting to write to the cached log.txt file while the web
generation also attempts to upload (read) the same log.txt file via FTP, and vice-versa. HFM will attempt either operation multiple times before timing out and
also fail graciously in lieu of tearing the process down. Neither I/O operation is critical to the long term health of the process.
HFM.NET v0.9.7.558
Download Location on Google Drive: https://drive.google.com/open?id=0B8d5F59S5sCiS1RISzdsaEd5UXM
- Change: Reworked HFM's FAH Log File Parsing API. Changes targeted to make v7 log files a first class citizen in lieu of of being a derivation of v6 logs.
As a result HFM as a client application does much less repeated parsing and scanning of the log data which results in less memory usage and faster client data processing.
I'm also curious to see how well GPU work unit failures are now captured from v7 clients. I don't have any modern GPUs so this is obviously difficult for me to test.
- Change/Fix: Replaced the preferences/configuration storage mechanism (user.config) which has been a source of random problems since HFM's inception.
Existing preferences will migrate to the new (home rolled) storage mechanism. The new preferences can be found in the HFM data files folder (config.xml).
- Fix: Crash reported by john on the hfm-net Google Group. He discovered a race condition between HFM attempting to write to the cached log.txt file while the web
generation also attempts to upload (read) the same log.txt file via FTP, and vice-versa. HFM will attempt either operation multiple times before timing out and
also fail graciously in lieu of tearing the process down. Neither I/O operation is critical to the long term health of the process.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages