EvilAlchemist
2[H]4U
- Joined
- Jan 11, 2008
- Messages
- 2,730
Currently, there is an issue with FAHmon 2.3.4 using very high CPU %.
When the clients are "refreshed", the CPU will spike, sometimes using a entire CPU core.
In the last few versions of FAHmon, the program switched from using the unitinfo.txt to FAHlog.txt to get the status of the client.
It has been determined that the FAHlog.txt file size is the issue.
This seems to happen more on GPU2 clients, but can happen to other clients as well.
I checked my GPU2 FAHlog.txt files and some were over 800K.
(Client has been running for over a month)
In my setup, all this data must go over my lan, so load times get extremely long with the amount of clients I am running.
(If all data was on the local system, this would not really be an issue)
If you are getting long load times, or FAHmon is spiking you CPU, shut down the client and delete the FAHlog.txt.
The client will create a new FAHlog.txt on restart.
This is a temporary workaround until a more permanent solution can be implemented.
When the clients are "refreshed", the CPU will spike, sometimes using a entire CPU core.
In the last few versions of FAHmon, the program switched from using the unitinfo.txt to FAHlog.txt to get the status of the client.
It has been determined that the FAHlog.txt file size is the issue.
This seems to happen more on GPU2 clients, but can happen to other clients as well.
I checked my GPU2 FAHlog.txt files and some were over 800K.
(Client has been running for over a month)
In my setup, all this data must go over my lan, so load times get extremely long with the amount of clients I am running.
(If all data was on the local system, this would not really be an issue)
If you are getting long load times, or FAHmon is spiking you CPU, shut down the client and delete the FAHlog.txt.
The client will create a new FAHlog.txt on restart.
This is a temporary workaround until a more permanent solution can be implemented.