Summary: | Problem with optimizing sci-misc/boinc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | M. LaPlante <bugzilla> |
Component: | Current packages | Assignee: | Marcus D. Hanwell (RETIRED) <cryos> |
Status: | RESOLVED UPSTREAM | ||
Severity: | trivial | CC: | herber, xyzzy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Other | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
M. LaPlante
2006-03-16 09:56:33 UTC
I really fail to see why is this a Gentoo bug... Because it's specific to the Gentoo ebuilds... Distros with precompiled apps obviously would not have this issue. (In reply to comment #2) > Because it's specific to the Gentoo ebuilds... > > Distros with precompiled apps obviously would not have this issue. So, how upstream awards some credits it Gentoo's fault. Really makes sense. Well, so compile it for i386 with some stupid counter-optimizations and you'll get more credits. (In reply to comment #3) > So, how upstream awards some credits it Gentoo's fault. Really makes sense. > Well, so compile it for i386 with some stupid counter-optimizations and Sure, the BOINC credit mechanism could be improved, but it's always going to be imperfect. That doesn't mean that the gentoo ebuild should make the problem worse! The BOINC core client downloads and schedules other application binaries. The build environments of the core client and those other applications are all different, and the whole thing is cross platform, cross architecture. That's why assigning fair credits is a difficult problem. There's *no* advantage to building an optimised core client, because the program doesn't do the grunt work itself. Instead, an optimised client disadvantages gentoo users. On average, they'll get less credit for the same work. This will affect some projects more than others; it will be worst for a project like ClimatePrediction.net where the credit isn't averaged over redundant results. People like their credits. Why not be as fair as possible? A fair solution would seem to be: use any optimisations that are supplied by upstream, but strip out the user-supplied ones. That would put gentoo boinc on a par with generic binaries. By the way, this isn't just a gentoo problem. Any distribution which packages the core client as a binary faces the same issue: what optimisation to use when building it. Tell upstream that their crediting system sucks... |