Well, that's seems true. I have dual PIII machine.
On one CPU I run wine+boinc, on the second pure linux client. reults:
wine: 40Ksek
linux: 37Ksek
Is now linux cruncher faster than windows ???
I don't know what You mean by wall-clock time, but both clients run simultaneously on the same machine (running gentoo linux) This is dual p3@1400MHz. here's current stats
for the wine:
Measured floating point speed 1254.83 million ops/sec
Measured integer speed 3154.52 million ops/sec
Average upload rate 1.73 KB/sec
Average download rate 325.02 KB/sec
Average turnaround time 0.85 days
Maximum daily WU quota per CPU 8/day
% of time BOINC client is running 98.1027 %
While BOINC running, % of time work is allowed 98.5449 %
last WU 40,798.67
for the pure linux
Measured floating point speed 737.42 million ops/sec
Measured integer speed 1480.51 million ops/sec
Average upload rate 1.42 KB/sec
Average download rate 210.49 KB/sec
Average turnaround time 0.72 days
Maximum daily WU quota per CPU 8/day
% of time BOINC client is running 99.7148 %
While BOINC running, % of time work is allowed 100 %
last WU 36,920.87
amazing !
On one machine I stopped one wine+boinc and run pure linux.
The CPU seconds needed to crunch unit dropped from 88K to 80K.
Hence claimed only 96 credits instead 112...
The "CPU time" is the time that is counted by the App, reported to the Client and put into the database for the result. It is the time the App would take to run if it would have the whole CPU 100% of the time, which is usually not the case on modern multi-tasking OS.
The "wallclock-time" is the time that it actually passes while computing a workunit (which of course depends on what else is going on on the system), so the difference between the timestamps of the messages "Starting result xxx" and "Computation for result xxx finished".
I am not completely sure, but I think BOINC still sees Wine as a Win9x system, which leads it to use a CPU time counter which is not very accurate.
Seriously, best you can do is to write down the times when the WU starts and then track it that way. If you have 5 projects with equal resource shares the proportion of wall clock to CPU Time should be about 5 to 1 ...
The new Linux Cruncher is running Great!
)
Yes. Very well done!
I'am from 42K down to 30K on an AMD XP 2600+
Thanks,
Michael
Team Linux Users Everywhere
Maybe it's time I re-attached
)
Maybe it's time I re-attached E@H to my Linux-BOINC...
Well, that's seems true. I
)
Well, that's seems true. I have dual PIII machine.
On one CPU I run wine+boinc, on the second pure linux client. reults:
wine: 40Ksek
linux: 37Ksek
Is now linux cruncher faster than windows ???
Wouldn't surprise me. If this
)
Wouldn't surprise me. If this is CPU-time (which I assume), how is the wall-clock time?
BM
BM
RE: Dropped my crunchtime
)
Which is useful since you'll be doing a lot more CPU processing on THIS side of BOINC, eh? (smile).
I don't know what You mean by
)
I don't know what You mean by wall-clock time, but both clients run simultaneously on the same machine (running gentoo linux) This is dual p3@1400MHz. here's current stats
for the wine:
Measured floating point speed 1254.83 million ops/sec
Measured integer speed 3154.52 million ops/sec
Average upload rate 1.73 KB/sec
Average download rate 325.02 KB/sec
Average turnaround time 0.85 days
Maximum daily WU quota per CPU 8/day
% of time BOINC client is running 98.1027 %
While BOINC running, % of time work is allowed 98.5449 %
last WU 40,798.67
for the pure linux
Measured floating point speed 737.42 million ops/sec
Measured integer speed 1480.51 million ops/sec
Average upload rate 1.42 KB/sec
Average download rate 210.49 KB/sec
Average turnaround time 0.72 days
Maximum daily WU quota per CPU 8/day
% of time BOINC client is running 99.7148 %
While BOINC running, % of time work is allowed 100 %
last WU 36,920.87
amazing ! On one machine I
)
amazing !
On one machine I stopped one wine+boinc and run pure linux.
The CPU seconds needed to crunch unit dropped from 88K to 80K.
Hence claimed only 96 credits instead 112...
wijata.com: The "CPU time"
)
wijata.com:
The "CPU time" is the time that is counted by the App, reported to the Client and put into the database for the result. It is the time the App would take to run if it would have the whole CPU 100% of the time, which is usually not the case on modern multi-tasking OS.
The "wallclock-time" is the time that it actually passes while computing a workunit (which of course depends on what else is going on on the system), so the difference between the timestamps of the messages "Starting result xxx" and "Computation for result xxx finished".
I am not completely sure, but I think BOINC still sees Wine as a Win9x system, which leads it to use a CPU time counter which is not very accurate.
BM
BM
How do I check the
)
How do I check the wallclock-time ?
A stopwatch? :) A wall
)
A stopwatch? :)
A wall clock? :)
Seriously, best you can do is to write down the times when the WU starts and then track it that way. If you have 5 projects with equal resource shares the proportion of wall clock to CPU Time should be about 5 to 1 ...