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.
Sorry, I messed up my previous posting (evreything after "<" got lost) - text should be:
From what you write I suspect that you are running a Linux kernel 2.6.x with x < 10 (which seems to be true). "top" there doesn't report correct values for multi-threaded programs (like einstein), so don't trust it - or upgrade your kernel.
Why does it only seem to affect Einstein, or what is Einstein doing differently.
Einstein is the only BOINC App I currently know of that has graphics on Linux, resulting in a multi-threaded program (even if you don't show the graphics). All other projects are, I think, single-threaded, so this top bug doesn't apply there.
BTW: you shouldn't need to upgrade your kernel to _run_ E@H.
Has anyone else to get BOINCManager to display the Einstein graphics?
Probably not. I just found a problem in the build process, most likely nobody is able to load the graphics library right now. Too bad that no one caught this in the beta test. But a solution is on the way and should result in a new App soon.
Has anyone else to get BOINCManager to display the Einstein graphics?
Probably not. I just found a problem in the build process, most likely nobody is able to load the graphics library right now. Too bad that no one caught this in the beta test. But a solution is on the way and should result in a new App soon.
BM
Disagree, i can see graphics in the Manager.
Pretty surprising. What Linux Distri / Kernel are you running? All your current hosts are listet as running Windows - remember that this thread is about the Linux App.
Sorry, was a bit too hastily - it seems that only the latest Linux Beta App is affected, the prvious 0.06 now standard 4.81 is built with slightly older BOINC code and shouldn't have that problem.
The new Linux Cruncher is running Great!
)
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
RE: After some more
)
That's really surprising, as the Windows App should favour the Intel (P4) a bit.
True, but the SSE is present in both (modern) types of CPUs. (btw: The App didn't gain much from SSE2 compared to SSE)
This may depend on the CPUs as well as the Linux kernel and Wine version. wijata.com, what were the systems you made this observation on?
BM
BM
PCZ: From what you write I
)
PCZ:
From what you write I suspect that you are running a Linux kernel 2.6.x with x <
BM
Sorry, I messed up my
)
Sorry, I messed up my previous posting (evreything after "<" got lost) - text should be:
From what you write I suspect that you are running a Linux kernel 2.6.x with x < 10 (which seems to be true). "top" there doesn't report correct values for multi-threaded programs (like einstein), so don't trust it - or upgrade your kernel.
BM
BM
RE: Why does it only seem
)
Einstein is the only BOINC App I currently know of that has graphics on Linux, resulting in a multi-threaded program (even if you don't show the graphics). All other projects are, I think, single-threaded, so this top bug doesn't apply there.
BTW: you shouldn't need to upgrade your kernel to _run_ E@H.
BM
BM
PCZ: You may want to try our
)
PCZ:
You may want to try our new Beta App (see this thread). It contains newer BOINC code that may fix your problem.
BM
BM
RE: Has anyone else to get
)
Probably not. I just found a problem in the build process, most likely nobody is able to load the graphics library right now. Too bad that no one caught this in the beta test. But a solution is on the way and should result in a new App soon.
BM
BM
RE: RE: RE: Has anyone
)
Pretty surprising. What Linux Distri / Kernel are you running? All your current hosts are listet as running Windows - remember that this thread is about the Linux App.
BM
BM
Sorry, was a bit too hastily
)
Sorry, was a bit too hastily - it seems that only the latest Linux Beta App is affected, the prvious 0.06 now standard 4.81 is built with slightly older BOINC code and shouldn't have that problem.
BM
BM