Not your imagination at all - the benchmark code in BOINC doesn't fare as well under Linux/Unix, as compared to Windows. Since claimed credit is a function of the sum of the two benchmarks multiplied by processing time, that suffers as well. The difference used to be much worse with the one of the previous versions of the BOINC code, and efforts have been underway to sort the benchmarking business once and for all. A matter of time...
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Not your imagination at all - the benchmark code in BOINC doesn't fare as well under Linux/Unix, as compared to Windows. Since claimed credit is a function of the sum of the two benchmarks multiplied by processing time, that suffers as well. The difference used to be much worse with the one of the previous versions of the BOINC code, and efforts have been underway to sort the benchmarking business once and for all. A matter of time...
Seems to me there are two distinct issues:
1. Given the same hardware and work unit, I would expect a result in
approximately the same amount of time regardless of OS. This was
nowhere near happening when I first looked at e@home but it now seems
to be more or less Ok.
2. Given a work unit, I would expect any computer to claim approximately
the same credit regardless of hardware or OS. This doesn't seem to be the
case. The bizarreness of it all is that you can have 6 identical hardware
configs - 3 Windows and 3 Linux. If 3 Windows hosts process the WU, they
will receive more credit than 3 Linux host processing the same WU.
1. Given the same hardware and work unit, I would expect a result in
approximately the same amount of time regardless of OS. This was
nowhere near happening when I first looked at e@home but it now seems
to be more or less Ok.
2. Given a work unit, I would expect any computer to claim approximately
the same credit regardless of hardware or OS. This doesn't seem to be the
case. The bizarreness of it all is that you can have 6 identical hardware
configs - 3 Windows and 3 Linux. If 3 Windows hosts process the WU, they
will receive more credit than 3 Linux host processing the same WU.
1. How do you know your computers have the "exact" same work unit? In E@H there are 3 types of workunits right now, and each vary wildly in the amount of relative time it takes to complete each one.
2. As said before, this is because you are probably not using "optimized" boinc client. When you first run boinc it tests your computer's speed(this independent of E@H). If you are using the ordinary i386 binaries for Linux, then it isn't showing the real benchmark of the system.
such things just should not be writ so please destroy this if you wish to live 'tis better in ignorance to dwell than to go screaming into the abyss worse than hell
Now everyone get back to work and stop overanalyzing.
Calm down.
such things just should not be writ so please destroy this if you wish to live 'tis better in ignorance to dwell than to go screaming into the abyss worse than hell
Now everyone get back to work and stop overanalyzing.
Calm down.
No happy pill today huh?
I am the one having fun :) No pills even!
such things just should not be writ so please destroy this if you wish to live 'tis better in ignorance to dwell than to go screaming into the abyss worse than hell
Now everyone get back to work and stop overanalyzing.
Calm down.
No happy pill today huh?
I am the one having fun :) No pills even!
I don't get too much time on the message boards, but I would be very much a happy camper if someone told me of a windows optimized client for E@H. Does such a thing exist, and where can I find it? How much better are the results of said upgrade?
1. How do you know your computers have the "exact" same work unit? In E@H there are 3 types of workunits right now, and each vary wildly in the amount of relative time it takes to complete each one.
It's not hard to compare how other different computers handle the same work unit the results are published. Eventually you get a feel for how your computer(s) performs against other similar ones (hardware). With the early e@home clients my Linux system was taking way longer to produce a result than much slower computers running Windows. I lost interest at that point - if I was going to contribute to global (and local) warming I expected the e@home developers to maximize the return per unit of pollution. With the current e@home client Linux
clients are at least in the same ball park as Windows ones.
Quote:
2. As said before, this is because you are probably not using "optimized" boinc client. When you first run boinc it tests your computer's speed(this independent of E@H). If you are using the ordinary i386 binaries for Linux, then it isn't showing the real benchmark of the system.
My Linux computer seems to produce results as efficiently as a Windows one. It is an anomaly that it doesn't claim as much credit as a similar computer running Windows, but it doesn't bother me too much.
Now everyone get back to work and stop overanalyzing.
Calm down.
No happy pill today huh?
I am the one having fun :) No pills even!
I don't get too much time on the message boards, but I would be very much a happy camper if someone told me of a windows optimized client for E@H. Does such a thing exist, and where can I find it? How much better are the results of said upgrade?
Gerry Rough
ATM, there is no E@H optimized app. THis is b/c the science app isn't open source.
Is it just my imagination .....
)
Not your imagination at all - the benchmark code in BOINC doesn't fare as well under Linux/Unix, as compared to Windows. Since claimed credit is a function of the sum of the two benchmarks multiplied by processing time, that suffers as well. The difference used to be much worse with the one of the previous versions of the BOINC code, and efforts have been underway to sort the benchmarking business once and for all. A matter of time...
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: Not your imagination at
)
Seems to me there are two distinct issues:
1. Given the same hardware and work unit, I would expect a result in
approximately the same amount of time regardless of OS. This was
nowhere near happening when I first looked at e@home but it now seems
to be more or less Ok.
2. Given a work unit, I would expect any computer to claim approximately
the same credit regardless of hardware or OS. This doesn't seem to be the
case. The bizarreness of it all is that you can have 6 identical hardware
configs - 3 Windows and 3 Linux. If 3 Windows hosts process the WU, they
will receive more credit than 3 Linux host processing the same WU.
RE: 1. Given the same
)
1. How do you know your computers have the "exact" same work unit? In E@H there are 3 types of workunits right now, and each vary wildly in the amount of relative time it takes to complete each one.
2. As said before, this is because you are probably not using "optimized" boinc client. When you first run boinc it tests your computer's speed(this independent of E@H). If you are using the ordinary i386 binaries for Linux, then it isn't showing the real benchmark of the system.
such things just should not be writ so please destroy this if you wish to live 'tis better in ignorance to dwell than to go screaming into the abyss worse than hell
Here's a specific, actionable
)
Here's a specific, actionable solution !
Download & run optimized linux client: http://www.guntec.de/Crunch3r/boincx86.html
See claimed credit rise. How much? Check out my WU's reported March 2 and note how it triples.
http://einsteinathome.org/host/555885/tasks
Now everyone get back to work and stop overanalyzing.
RE: Now everyone get back
)
Calm down.
such things just should not be writ so please destroy this if you wish to live 'tis better in ignorance to dwell than to go screaming into the abyss worse than hell
RE: RE: Now everyone get
)
No happy pill today huh?
RE: RE: RE: Now
)
I am the one having fun :) No pills even!
such things just should not be writ so please destroy this if you wish to live 'tis better in ignorance to dwell than to go screaming into the abyss worse than hell
RE: RE: RE: RE: Now
)
I don't get too much time on the message boards, but I would be very much a happy camper if someone told me of a windows optimized client for E@H. Does such a thing exist, and where can I find it? How much better are the results of said upgrade?
Gerry Rough
(Click for detailed stats)
RE: 1. How do you know
)
It's not hard to compare how other different computers handle the same work unit the results are published. Eventually you get a feel for how your computer(s) performs against other similar ones (hardware). With the early e@home clients my Linux system was taking way longer to produce a result than much slower computers running Windows. I lost interest at that point - if I was going to contribute to global (and local) warming I expected the e@home developers to maximize the return per unit of pollution. With the current e@home client Linux
clients are at least in the same ball park as Windows ones.
My Linux computer seems to produce results as efficiently as a Windows one. It is an anomaly that it doesn't claim as much credit as a similar computer running Windows, but it doesn't bother me too much.
RE: RE: RE: RE: Quote
)
ATM, there is no E@H optimized app. THis is b/c the science app isn't open source.
Kathryn
Kathryn :o)
Einstein@Home Moderator