I tested it. It seems the issue is that python 3.8 was the final version to be compatible with Windows 7.

We built the application using python 3.13.2.

3.8 is no longer supported by Python's developers. It received its final security update last year.

I'm going to see if we can even use 3.8 (technically), but since it's not supported even for security updates anymore, and those security updates were only provided via source and not via binary installers, I don't see a feasible way to use python 3.8.

Regardless, I'll update here again when I have a final answer.

Some tasks took longer to complete than others. A task was done only 18.1% in 12 hours. Is the 72 hour time limit enough for these longer tasks if an older cpu is used?

<active_task>
<project_master_url>https://minecraftathome.com/minecrafthome/</project_master_url>
<result_name>xoroshigo_2.07_config-053-hxlreg-fullinfo-rank005-tamTZ5DN_12_1</result_name>
<checkpoint_cpu_time>42419.640000</checkpoint_cpu_time>
<checkpoint_elapsed_time>43232.707571</checkpoint_elapsed_time>
<fraction_done>0.181150</fraction_done>
<peak_working_set_size>171810816</peak_working_set_size>
<peak_swap_size>932249600</peak_swap_size>
<peak_disk_usage>50141965</peak_disk_usage>
</active_task>

I too am seeing much, much longer completion time estimates and progress percentages than all the prior tasks. The slower cpus are not going to be able to complete tasks within the current deadlines.

Also, is the credit awarded going to be commensurate with the longer compute times needed. We're talking a 10X factor here at least compared to the credit awarded for the prior series of tasks that took 1 hour on modern cpus.

Several others already past 12 hours of computation time and most not yet to 50% completion. The Epyc cpus 7713 and 7B13 can only manage around 2Ghz so those ones are in danger of not completing in 72 hours.

An example on a Ryzen 9950X cpu running north of 5.2 Ghz.

Application
Xoroshiro128++ Guessing Order Optimization v1.1 1.04 (lin-modern)
Name
xoroshigo_2.07_config-056-hxlreg-fullinfo-rank010-CKW3GEjN_17
State
Running
Received
Sun 13 Apr 2025 05:06:43 PM PDT
Report deadline
Wed 16 Apr 2025 05:06:42 PM PDT
Estimated computation size
29,100 GFLOPs
CPU time
14:30:43
CPU time since checkpoint
---
Elapsed time
14:36:42
Estimated time remaining
21:08:23
Fraction done
40.870%
Virtual memory size
4.39 GB
Working set size
175.94 MB
Directory
slots/3
Process ID
42178
Progress rate
2.880% per hour
Executable
xoroshigo2_wrapper_1.04_x86_64-pc-linux-gnu.bin

Wow! was wondering why my points/hour tanked
lol

For this longer task, if I don't turn off SMT on the 9950X and just run 16 tasks at once, it likely won't finish before the deadline.

Application
Xoroshiro128++ Guessing Order Optimization v1.1 1.04 (win-modern)
Name
xoroshigo_2.07_config-053-hxlreg-fullinfo-rank005-tamTZ5DN_12
State
Running
Received
2025/4/14 7:25:05
Report deadline
2025/4/17 7:25:06
Estimated computation size
29,100 GFLOPs
CPU time
15:36:03
CPU time since checkpoint
---
Elapsed time
16:00:19
Estimated time remaining
2d 11:57:15
Fraction done
21.071%
Virtual memory size
889.06 MB
Working set size
163.79 MB
Directory
slots/21
Process ID
14404
Progress rate
1.440% per hour
Executable
xoroshigo2_wrapper_1.04_windows_x86_64.exe
Application Name
xoroshigo2
Plan Class
win-modern

Seeing extremely long runtimes on the CPU tasks now as well. Was wondering what the problem was. What was changed and why?

I'm seeing way more than 10x. 9950x was under an hour but I saw some ETA over a day.

I asked why the change in completion times on the project's Discord server from the developer.

This is his reply.

"The summary is that each config file tells the app to search with different sets of constraints. When developing the app I made sure to track the total number of loop iterations to ensure each version ran for the same amount of time, no matter how large of a space it was asked to search. My method seemed to work perfectly for the first 50 or so config files we sent out, but there seems to be some kind of pathological case that's screwing it up."

No response after that so don't know whether they are working on a fix for this in a new app, or whether they are going to adjust the deadline dates or what?

The News sub-topic has the developer's answer on what happened with these tasks and the current investigation into their intended fix.
https://minecraftathome.com/minecrafthome/forum_thread.php?id=212&postid=1145