Folding Forum

When everyone gets the same mix of work units, the competition is still fair. We all have to fold those, so you are not put to a disadvantage. You can still compete on the same level.

I have seen reference to "making up a batch of wu" so we can run them, does anyone know how many 8018's are in this batch. A countdown ticker would be great. My 3 780 ti's have been running them for 7 days I am not complaining.

Thanks,
Ben

kimben777 wrote:...does anyone know how many 8018's are in this batch. A countdown ticker would be great.

I would be happy to have this information for all projects, core_17 or not, just as a matter of curiosity and as a satisfier of my OCD need for orderly completion.
It could even reset frequently as new work is added to the project, that wouldn't bother me, I'd just be curious to see progress beyond my own work unit(s)

Doesn't exist. Even if it did, it would not help much, as another batch could come along at any minute. Or not. Or again. A project keeps adding batches until no more batches are needed. A count down doesn't work so well when the count keeps changing. Bells with little benefit get the lowest priority. Whistles none at all.

7im wrote:Bells with little benefit get the lowest priority. Whistles none at all.

Conceded; software optimization beats all and I'm sure the team is already flooded with work on that front (e.g. Maxwell)

Kurtis200200 wrote:... I'm sure the team is already flooded with work on that front (e.g. Maxwell)

No, you misunderstand.

The driver bug for Maxwell is in NVidia's hands, not Stanford's. The FAH team is flooded with other priorities and like all of us, is waiting (im-)patiently for NVidia to fix the problem with Maxwell's OpenCL drivers.

The beginning of this blog was about people who have upgraded hardware for the future of FAH and are just getting core 15 wu's. Why so many core 15 wu's when the near future is core 17? Kepler is working fine.

Ben

kimben777 wrote:Why so many core 15 wu's when the near future is core 17?

Because it's not possible to change a running project from one core to another. Started projects on core 15 need to finish. New one will be core 17. Until we crunched away all required WU from core 15 they will be around therefore as quick we crunch them as better it is.

In addition to not being able to switch a project from one core to another, a project can take one or more years to complete. For example, Project 8018 which has been mentioned frequently in this topic was released to beta testing about 2 years ago.

Since 8018 is still running after all this time, it must be producing valuable, maybe millisecond timescale data that will generate a valuable scientific paper!

kimben777 wrote:The beginning of this blog was about people who have upgraded hardware for the future of FAH and are just getting core 15 wu's. Why so many core 15 wu's when the near future is core 17? Kepler is working fine.

Ben

With the above few posts repeating the same answer again as it appeared on the first few pages of this thread, please consider the question asked and answered once again.

Are donors still seeing lots of Core15 on Kepler? We made some AS changes some time ago and thought that issue was resolved.

I have fermi's (GTX 460's and GTX 580's) and am certainly seeing constant p8018's. Your fix produced Core_17 projects for a few days and then it reverted back.

VijayPande wrote:Are donors still seeing lots of Core15 on Kepler? We made some AS changes some time ago and thought that issue was resolved.

How does anyone tell if any GPU projects are running when new GPU projects are not announced on this forum, and the new servers do not show up in the Server Status Page?

7im wrote:How does anyone tell if any GPU projects are running when new GPU projects are not announced on this forum, and the new servers do not show up in the Server Status Page?

Only indirectly, extrapolating via the volume of core_15-related posts on this and other fora