small x in stderr file
22 Aug 2006 6:33:22 UTC
Topic 191717
(moderation:
Can someone tell me what the small x is in reference to in this result file. http://einsteinathome.org/task/39922885
This has just surfaced resently.
Thank you
small x in stderr file
)
The answer by Bernd:
It's a bit complicted to describe what it means mathematically, but this is written when a special case is called in the program. I knew that this would occur very rarely, but I wanted to see how often it actually happens in the "real world" to see if it's worth to optimize that part of the code, too.
Dead men don't get the baby washed. HTH
Hmmm.... OK, I have
)
Hmmm....
OK, I have averaged 6.37 "small x"'s over the 19 results I have showing, ranging from none to 63 per WU.
Whatever that means! :-)
Alinator
Since there're ~50k potential
)
Since there're ~50k potential small x's per large wu, it basically means that Bernd was correct in assuming it was too rare a case to bother optimizing.
I'm curious though, how much the debug check in the current build hurts performance. I honestly expected it to be removed from the release version of the app.
RE: I'm curious though, how
)
The case distinction is always in there and - as shown by the "small x" occurrencies - obviously needs to be. I'm rather suprised how often this occurs - I actually hoped that I could completely drop this case (and the test with it), at least for a predictable category of Workunits. Pitty I can't.
Writing the line in stderr is the only difference to the previous code and doesn't take much time.
BM
BM
My Merom produces small x
)
My Merom produces small x too.
http://einsteinathome.org/task/40122416
Well at least I'm not alone,
)
Well at least I'm not alone, thought it might have been some sort of flag or error. This machine averages 20.1 small x / wu.