Folding Forum

After discussions, we've decided to raise up the final deadline time, by about 30%, so that should solve some of the problems on this thread. Are not adjusting the preferred deadline time quite yet, or the points. Still evaluating that!

Thanks for the report. 3867 should be the same as 3866, so that's strange that is behaving so poorly. It's actually at very low weight compared to the others, so I'll take it off until we understand better what is going on.

Thanks very much for all this information. Most of the WU are returning just fine, but there are a small but nonnegligible fraction that are having these unexplained crashes. We're still in the process of trying to replicate and fix this bug -- it's one of those horrible bugs where when you even put...

This series does take a long time - from 44 hours for my 2 GHz dual-core laptop to 77 hours for my 3.0 GHz P4 to 110 hours for my 2.0 GHz Sempron. None report SSE but all report "Assembly optimizations on if available." 333 points seems a little low but better than some others. Hmm. It se...

I don't think SSE is the issue here, because -forceasm is being used. The line 01:55:49:Unit 01:- Assembly optimizations manually forced on. Indicates that any problem there is being ignored. If it IS the issue deleting the core.dat file should eliminate this; that's the file that stores that inform...

Hi, Bruce- Right now, the problem is that it usually returns correctly from a checkpoint. It appears to occasionally fail, but in beta, we couldn't collect enough information to actually figure out when it fails. It might be best to pull it back to advanced, however - that will presumably allow us t...

So, Client 7, on Windows XP. I don't think we've tested that combination, so that might be the reason. Is this replicatable? Can if you get another WU (near the beginning, hopefully!) and see if it crashes, that would be very valuable!

By "startup" I mean restarting on checkpoint.

So, this is dying only on startup, correct?

The stats for 3865-3867 are indeed set up to give a bonus. Note that because of some quirks of hard coding, A6 can only be used on SMP using the v7 client (now in beta).

Well, that was quick. As soon as I posted, the power went back on. Server is now restarted and reloading all the jobs, should be fine (unless the storm starts another blackout).

There's an ongoing power outage in the building housing the machines 128.143.48.226 and 128.143.48.227 (the collection server for 128.143.48.226), starting at about 5 p.m. today. (2.5 hours ago). They were on battery backup, but not emergency power, so I had to shut them down. Hopefully the power wi...

The scientific core is designed to autodetect the presence of SSE2, and only run SSE2 instructions if they are applicable; this works on the machines I tested with.

Perhaps if the CPU is old enough (not even SSE), then the signal used to detect SSE2 is not available, and it defaults to SSE2?

A error in the new server cropped up in parsing some assignment server instructions. A workaround has been implemented, and the server restarted. It should show up as soon as it processes all the new jobs.

It was not showing the CS because of the difference in configuration files in the new and old server code. I've put a fix in place so that the CS now gets listed.