log in |
1)
Message boards :
Number crunching :
Trial Factoring
(Message 9372)
Posted 10 Dec 2023 by Luminescence You can ignore that: Looking at mfakto's source, it should work as well. Takes the same -d argument. Unfortunately I can't test this stuff, as I don't have a multi-gpu system. Not too sure if it works with the app_config.xml, someone else would have to try. |
2)
Message boards :
Number crunching :
Trial Factoring
(Message 9370)
Posted 10 Dec 2023 by Luminescence I've looked into the "device 0" issue. Under https://boinc.berkeley.edu/trac/wiki/WrapperApp it is stated: command_line The current jobfile only contains <task>
<application>mfaktc-win-64.exe</application>
<append_cmdline_args/>
</task> mfaktc ignores any command-line arguments it doesn't know, so it ignores the appended --device N passed to the wrapper.Could the following change to the jobfile work? <task>
<application>mfaktc-win-64.exe</application>
<command_line>-d $GPU_DEVICE_NUM</command_line>
</task> The wrapper should replace $GPU_DEVICE_NUM with the device number it is passed from the BOINC client and mfaktc recognizes the argument -d. Otherwise it would be trivial to get mfaktc to recognize --device. |
3)
Message boards :
Number crunching :
Trial Factoring
(Message 8624)
Posted 6 Jan 2023 by Luminescence Thx for the hint, I have updated a new app version with the latest ini file, also used a very old file from yesterday as the wrapper. Sweet! The DLL insanity was a real pain if you did not have the toolkit installed. |
4)
Message boards :
Number crunching :
Trial Factoring
(Message 8622)
Posted 6 Jan 2023 by Luminescence Can you change the mfaktc.ini configuration? GPU Sieve Size is set to 64, but the version supports up to 2047. There is quite a bit of performance to be gained with that change. Not to mention the godawful coil whine my 4090 produces with this low amount. |