// DBOINCP-300: added node comment count condition in order to get Preview working ?>
Hugh L. McEntire
Joined: 23 May 05
Posts: 10
Credit: 9935
RAC: 0
6 Jun 2005 16:03:59 UTC
Topic 189299
(moderation:
)
The time reported in the CPU time is just half the real elapsed time. Is this normal or do I have a problem? I am only running Einstein and it is set for 100%. Hugh
The time reported in the CPU time is just half the real elapsed time. Is this normal or do I have a problem? I am only running Einstein and it is set for 100%. Hugh
Just remember, CPU time does not equal wall clock time. For the most part, the science apps run at "low priority". That means idle time type priority. This is by design, so if you are using your computer and have boinc running all the time (like I do), I don't usually notice that it is running as Windows/Linux/etc will let other programs have higher priority access to the cpu.
The time reported in the CPU time is just half the real elapsed time. Is this normal or do I have a problem? I am only running Einstein and it is set for 100%. Hugh
Just remember, CPU time does not equal wall clock time. For the most part, the science apps run at "low priority". That means idle time type priority. This is by design, so if you are using your computer and have boinc running all the time (like I do), I don't usually notice that it is running as Windows/Linux/etc will let other programs have higher priority access to the cpu.
James
Thanks James, I'm glad that it is normal and that I do not have a problem.
Hugh
The time reported in the CPU time is just half the real elapsed time. Is this normal or do I have a problem? I am only running Einstein and it is set for 100%. Hugh
Just remember, CPU time does not equal wall clock time. For the most part, the science apps run at "low priority". That means idle time type priority. This is by design, so if you are using your computer and have boinc running all the time (like I do), I don't usually notice that it is running as Windows/Linux/etc will let other programs have higher priority access to the cpu.
James
Thanks James, I'm glad that it is normal and that I do not have a problem.
Hugh
I was wondering if I have to run update whenever a unit is 100% or will it be uploaded automatically. Hugh
I was wondering if I have to run update whenever a unit is 100% or will it be uploaded automatically. Hugh
Hugh, it will be automatically uploaded to the scheduling server the next time the Boinc program on your machine asks for more work. The request for more work interval is dependent on the 'Connect to network' setting under the 'Network Usage' heading in your 'General Preferences' section of your Einstein account. I believe the default is .1 days. Cheers, Rog.
The time reported in the CPU time is just half the real elapsed time. Is this normal or do I have a problem? I am only running Einstein and it is set for 100%. Hugh
Just remember, CPU time does not equal wall clock time. For the most part, the science apps run at "low priority". That means idle time type priority. This is by design, so if you are using your computer and have boinc running all the time (like I do), I don't usually notice that it is running as Windows/Linux/etc will let other programs have higher priority access to the cpu.
James
Hey, another NetWare engineer. Great to see you James. If we could only get BOINC ported onto our servers. What an addition to the grid that would be. You into writing NLM's?
Looks like he is inactive, but for those who mght be browsing through;
he was probably running a p4 with hyperthreading which crunches 2 units at the same time.
Regarding CPU vs. real time, for my results and it would seem to hold true for most other people I have seen, the CPU time is in real clock time... just in seconds, so divide by 60 (to get minutes) and then divide by 60 again (to get hour format).
Quote:
The time reported in the CPU time is just half the real elapsed time. Is this normal or do I have a problem? I am only running Einstein and it is set for 100%. Hugh
Just remember, CPU time does not equal wall clock time. For the most part, the science apps run at "low priority". That means idle time type priority. This is by design, so if you are using your computer and have boinc running all the time (like I do), I don't usually notice that it is running as Windows/Linux/etc will let other programs have higher priority access to the cpu.
Time
)
The time reported in the CPU time is just half the real elapsed time. Is this normal or do I have a problem? I am only running Einstein and it is set for 100%. Hugh
Just remember, CPU time does not equal wall clock time. For the most part, the science apps run at "low priority". That means idle time type priority. This is by design, so if you are using your computer and have boinc running all the time (like I do), I don't usually notice that it is running as Windows/Linux/etc will let other programs have higher priority access to the cpu.
James
The time reported in the CPU
)
The time reported in the CPU time is just half the real elapsed time. Is this normal or do I have a problem? I am only running Einstein and it is set for 100%. Hugh
Just remember, CPU time does not equal wall clock time. For the most part, the science apps run at "low priority". That means idle time type priority. This is by design, so if you are using your computer and have boinc running all the time (like I do), I don't usually notice that it is running as Windows/Linux/etc will let other programs have higher priority access to the cpu.
James
Thanks James, I'm glad that it is normal and that I do not have a problem.
Hugh
The time reported in the CPU
)
The time reported in the CPU time is just half the real elapsed time. Is this normal or do I have a problem? I am only running Einstein and it is set for 100%. Hugh
Just remember, CPU time does not equal wall clock time. For the most part, the science apps run at "low priority". That means idle time type priority. This is by design, so if you are using your computer and have boinc running all the time (like I do), I don't usually notice that it is running as Windows/Linux/etc will let other programs have higher priority access to the cpu.
James
Thanks James, I'm glad that it is normal and that I do not have a problem.
Hugh
I was wondering if I have to run update whenever a unit is 100% or will it be uploaded automatically. Hugh
I was wondering if I have to
)
I was wondering if I have to run update whenever a unit is 100% or will it be uploaded automatically. Hugh
Hugh, it will be automatically uploaded to the scheduling server the next time the Boinc program on your machine asks for more work. The request for more work interval is dependent on the 'Connect to network' setting under the 'Network Usage' heading in your 'General Preferences' section of your Einstein account. I believe the default is .1 days. Cheers, Rog.
RE: The time reported in
)
Hey, another NetWare engineer. Great to see you James. If we could only get BOINC ported onto our servers. What an addition to the grid that would be. You into writing NLM's?
Bob
Looks like he is inactive,
)
Looks like he is inactive, but for those who mght be browsing through;
he was probably running a p4 with hyperthreading which crunches 2 units at the same time.
Regarding CPU vs. real time, for my results and it would seem to hold true for most other people I have seen, the CPU time is in real clock time... just in seconds, so divide by 60 (to get minutes) and then divide by 60 again (to get hour format).