FAH: Linux client too slow?

[mgpaulus]

I have a Compaq P2-300 MMX running OS/2, and running the 3.24 FAH CLI under ODIN. (If you don't know, you don't want to know 😀). Anyway, it's crunching a P632_TZ3_NAT, and EMIII is reporting 22.42 minutes per frame.
Sitting right next to it, I have an IBM 660E, 300 MHz P2, running Debian, w/a 2.4.19 kernel. It too is crunching a P632_TZ3_NAT, and EMIII is reporting it's taking 28.36 per frame.

I'm wondering whether I have something whacked on the Lappy, or whether the Linux client is just that much slower than the windows client.

The lappy kernel is reporting the CPU at 297.xx MHz, calibrated at 593.10 bogoMips.

 

[ProviaFan]

I don't know, but possibly the client is taking advantage of the MMX on the processor of the OS/2 machine. However, it would be a reasonable assumption that F@H on Windows will be faster than F@H on Linux, because the developers don't care about optimizing their client as much for a system that isn't used by as many people (look at the SETI@home client, it's the same way, only worse; the Windows client runs faster under WINE in Linux than the Linux client runs when native on Linux).

Sorry I can't help you more, I just set up the client under Linux myself earlier today, and will be setting up Samba so I can get KDFold to bench it vs. my Windows machine.

 

[mgpaulus]

I found that to effectively make samba work on my folding directories,
I needed to add the keyword 'force user = root' for my folding
shares. This allowed kdfold & EMIII to read/write to the directories
the way they wanted, since I run FAH3Console.exe from my startup
as root, which makes /work be drwxr-xr-x root root.

 

[mechBgon]

Ooops, nm 😱