Kidding???

Message boards : Questions and problems : Kidding???
Message board moderation

To post messages, you must log in.

AuthorMessage
Max Garth

Send message
Joined: 27 Nov 09
Posts: 27
Australia
Message 37801 - Posted: 14 May 2011, 9:07:09 UTC

Today I received an AP task that has a 76 hour time frame. Is this correct or has my use of the Throttle extended the time?????
MaxG.
ID: 37801 · Report as offensive
Profile Gundolf Jahn

Send message
Joined: 20 Dec 07
Posts: 1069
Germany
Message 37802 - Posted: 14 May 2011, 9:49:29 UTC - in response to Message 37801.  

76 hours sound reasonable for an AstroPulse task (I assume that's meant by AP), but if it's your first (in a longer time), the estimates might be far off.

Anyways, you're on the wrong forum here, since the AstroPulse application is run by the SETI@home project. Here at BOINC, no applications are run.

Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
ID: 37802 · Report as offensive
Max Garth

Send message
Joined: 27 Nov 09
Posts: 27
Australia
Message 37804 - Posted: 14 May 2011, 10:33:33 UTC - in response to Message 37802.  

Well I'm running Seti programs as well as Boinc but here is one for you, its now reading 309 hours, which is a bit of a joke really.
Max
ID: 37804 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15482
Netherlands
Message 37805 - Posted: 14 May 2011, 12:01:58 UTC

What Gundolf tried to tell you, is that this isn't really a BOINC problem and that you should be posting this on the Seti forums.

But it is easily explained: Your BOINC apparently never had an Astropulse task before, so it doesn't know how long these take. What you see is an estimated time to finish, not a real time. If you let it run, you'll see that the time will go down rather quickly.

Only by running several APs can BOINC learn how long they take on your system. No, the project cannot estimate it more correctly as there are a whole variety of computers out there which run these tasks in different time spans. If you still think that's wrong, then go complain at the project as it is they who send along the estimated time to run with the task.
ID: 37805 · Report as offensive
Max Garth

Send message
Joined: 27 Nov 09
Posts: 27
Australia
Message 37806 - Posted: 14 May 2011, 17:37:46 UTC - in response to Message 37805.  

Ageless....Come on I've been running this stuff for a years, I've had Astro Pulse stuff running out my ears, and I've NEVER seen an AP , aka Astro Pulse, task that was longer than 20 hours or so, prior to playing around with Throttle. And the program running in my box is Boinc, which allows it to handle Seti.
But that 309 hours is now 245 hours, it's lost about 60 hours already.
Aren't we on about the same thing.
If I might ask, me running Boinc means I am really running Seti so what the hell am I doing running Boinc, and what does it do anyway, if it doesn't muddle away with those bits of data that uploads into my box. Since I only run Seti tasks, just one project.
This is a Throttle problem, which is Boinc and not Seti.
It, these very long and variable hours associated with AP, and other tasks, never happened prior to me running Throttle, which might be of interest.
Normal computer operations, Boinc suspened, runs at 45C, on all 4 cores, but with a 4 core task runnning on Seti it goes up to 65 and with Throttle it is set at 60.
Throttle directly effects the time factor of ALL tasks. Which isn't at all what one expects. YOu wanted comments. This is just that.
MaxG.

ID: 37806 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15482
Netherlands
Message 37808 - Posted: 14 May 2011, 19:14:16 UTC - in response to Message 37806.  

BOINC is the managing program, it doesn't run any of the science. That's what the science applications do that you get by attaching to the different projects (for example, my BOINC is attached to 27 projects).

BOINC does show the estimated time to run of the tasks, but as soon as the project changes the run time of the tasks, this estimated time can easily be off.

Normal computer operations, Boinc suspened, runs at 45C, on all 4 cores, but with a 4 core task runnning on Seti it goes up to 65 and with Throttle it is set at 60. Throttle directly effects the time factor of ALL tasks. Which isn't at all what one expects. YOu wanted comments. This is just that.

TThrottle isn't a BOINC thing. It's a third party application made by Fred - efmer. You can complain about things you see go wrong with it here. But as the program name says, it throttles the science applications running under BOINC so your CPU doesn't overheat. So yes, tasks will take longer, since you do not let the CPU run at the full 100% all of the time.
ID: 37808 · Report as offensive
Claggy

Send message
Joined: 23 Apr 07
Posts: 1112
United Kingdom
Message 37819 - Posted: 15 May 2011, 9:12:05 UTC - in response to Message 37806.  

Normal computer operations, Boinc suspened, runs at 45C, on all 4 cores, but with a 4 core task runnning on Seti it goes up to 65 and with Throttle it is set at 60.

If you think your core temperatures are going up too high, isn't it a better idea to take the side off you computer and clear out the dust bunnies?
if the cores still run too hot when the science apps are running, try an after market cooler, good ones are so much more effiecient than the Stock coolers.

Claggy
ID: 37819 · Report as offensive

Message boards : Questions and problems : Kidding???

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.