Error rates and ECC

[kriesel]

Originally Posted by S485122

I'm sorry but I drown in your reference information, after two topics and three lines I am lost.

Well that's unfortunate, regardless of whatever level of exaggeration that might be present. I tried to use bold so someone in a hurry could skim quickly for the observed variations in error rate, then read a bit about any given value, or not. Maybe add some subheadings too?

if you want to evaluate the error rate of current contributions, you must not look at mismatches which might be a bad or a correct result (often proving a result from previous years bad.) Just look at recent LL results returned. Don't choose a range, don't limit yourself to a few results (as in "quite small sample sizes used"), evaluate the production of a whole year (using "text" for output will provide you with 10000 rows at a time).

I haven't analyzed it lately yet, but I suspect the current/recent error rate is somewhat a function of exponent. With a given error rate/unit time etc due to cosmic ray interactions or whatever, computations that take longer would have higher probability of error. Averaging together low exponent, medium, high, and very high, or fast, medium, slow and very slow runs, is likely to average together error rates that vary nonlinearly with exponent, & give a value that's inaccurate at either lowest or highest exponent range. On the other hand, statistical sampling error becomes an increasing problem as the available data gets sliced into smaller exponent range, application type, or date range bins. That effect can be estimated.

But those figures are what we are discussing, i.e. the current LL error rate and that current error rate is less than 0,7 %.

Well, in this thread, I suppose, since you originated it with the first post, about the past year, yes. And I think there are other ways of looking at it that are also useful. Not meaning to hijack the whole thread, and do appreciate the input from others. It's a big part of why I read the forum. The DDR generation being significant I had not thought of.

[chalsall]

Originally Posted by kriesel

Well that's unfortunate, regardless of whatever level of exaggeration that might be present.

If I may... Few appreciate the importance of curators.

I have known people who have PhDs who became curators, documenting others' work for future researchers.

It's a thankless job.

[Uncwilly]

Originally Posted by kriesel

I haven't analyzed it lately yet, but I suspect the current/recent error rate is somewhat a function of exponent.

Also, maybe you have an innate bias because you buy used equipment and run into errors. I have done runs on the same exponents as you and found the bad work that you have turned in. There have been several (IIRC) where you tried to self verify and had mismatches, ( again if memory serves, at least one of those was a PRP.) My error rate since 2009 is under 0.2%.

[xilman]

Originally Posted by chalsall

If I may... Few appreciate the importance of curators.

I have known people who have PhDs who became curators, documenting others' work for future researchers.

It's a thankless job.

I worked with several curators with doctorates during my time with FlyBase. They did receive thanks from those who appreciated the valuable work they did.

An admirable career for Aspie pedants, amongst whose ranks I include myself.

[kriesel]

Originally Posted by Uncwilly

you buy used equipment and run into errors

Actually a mix of new and used. And I may be running a larger than average-user proportion of larger exponents or longer runtimes. Part of the problem might be that I have too much Dell hardware. Or the wrong model numbers, or built on the wrong day by hungover line workers? Or high ambient temperatures sometimes. Who made your reliable hardware? My HP hardware seems more reliable.

[Uncwilly]

Originally Posted by kriesel

Who made your reliable hardware?

"Dude, I have (a) Dell."
Several actually

[Andrew Usher]

I can't help thinking Kriesel's use of GPUs probably contributes to his error rate; I doubt that with CPUs is out of line with the exponents he tests, but most of his bad results come from gpuowl (easily identified by its zero shift).