Astropulse & other long computing tasks


log in

Advanced search

Questions and Answers : Wish list : Astropulse & other long computing tasks

Author Message
RckR
Send message
Joined: 11 Jun 03
Posts: 3
Credit: 617,288
RAC: 1,055
Argentina
Message 1499776 - Posted: 4 Apr 2014, 17:49:33 UTC

It is 30Hs (processor time) and still 4 more to go (deadline in 5hs so is a lost battle with 30% CPU time ) and counting. I already lost another 20 hours 2 days ago.
Compute power (benchmark) & avg credit to put in High Priority with enough time in advance to complete the task, after the computing power & supposed time, put in high priority to give maybe double the time to finish the task.
Please Boinc check this. If you don't compute power & avg, at least put in High Priority 2 weeks in advance.

I have an I7-4700, 12GB, Win8.1 64.
Computing Preferences: 65% Processors, 35% CPU Time (I don't want to have the fan running at full speed all the time), Memory 40%. Use GPU (not valid for Astropulse yet). Min Work Buffer 1.25 Days, Max Add Wrk Buffer 1.25.

RckR, Guillermo_Alv
____________
Guillermo_Alv

rob smithProject donor
Volunteer tester
Send message
Joined: 7 Mar 03
Posts: 8555
Credit: 59,985,943
RAC: 92,860
United Kingdom
Message 1499788 - Posted: 4 Apr 2014, 18:02:50 UTC

A couple of comments
If you are running 35% CPU time then you can expect significant errors in the estimated duration, and significantly extended run times.
Are you running the stock applications, or one of the optimised applications?


Your buffer settings will have no impact on the execution times, but will impact on your ability to have a steady flow of work. It would be better to use min 1.5, plus 0.1.
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Profile BilBg
Volunteer tester
Avatar
Send message
Joined: 27 May 07
Posts: 2824
Credit: 6,363,725
RAC: 7,239
Bulgaria
Message 1500099 - Posted: 5 Apr 2014, 9:24:41 UTC - in response to Message 1499776.
Last modified: 5 Apr 2014, 9:29:46 UTC

35% CPU Time (I don't want to have the fan running at full speed all the time)

Return to 100% CPU Time and use TThrottle instead.
TThrottle is based on temperature (you set the max).
TThrottle uses much better method to reduce the CPU Time used (if/when the max temperature is reached) than BOINC

You have 'Computers hidden' - better unhide them when/if asking for help.


____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

Profile Ageless
Avatar
Send message
Joined: 9 Jun 99
Posts: 12338
Credit: 2,639,120
RAC: 1,240
Netherlands
Message 1500138 - Posted: 5 Apr 2014, 12:40:11 UTC

By telling BOINC to use 30% or 35% CPU time, you tell BOINC to run for only 18 and 21 minutes per 60 minutes. The way that BOINC uses CPU Time, the other 42 and 39 minutes it is suspended.

Which means that when we extrapolate that on the deadline, when running one task, on one CPU, it means that:
- for Multibeam v7 tasks you have 23 days to be able to finish them.
-- At 30% CPU Time, this means that you have 6.9 days (6 days, 21 hours, 36 minutes) to finish one task, when you run the computer 24 hours, 7 days a week.
-- At 35% CPU Time, this means that you have 8.05 days (8 days, 1 hour, 12 minutes) to finish one task, when you run the computer 24 hours, 7 days a week.

- for Astropulse v6 tasks you have 25 days to be able to finish them.
-- At 30% CPU Time, this means that you have 7.5 days (7 days, 12 hours) to finish one task, when you run the computer 24 hours, 7 days a week.
-- At 35% CPU Time, this means that you have 8.75 days (8 days, 18 hours) to finish one task, when you run the computer 24 hours, 7 days a week.

All these should be enough to finish the task, even at 30% or 35% CPU Time. If... BOINC is allowed to run 24 hours a day, 7 days a week.
When BOINC is not allowed to run constantly, the numbers increase exponentially. You can do the math from there.

65% of the processors of an i7-4700 means that you use either 2 CPU cores (without hyperthreading) or 4 CPU cores (with hyperthreading. The value for "Use at most X% of the processors" is an integer, meaning it will round down to the nearest whole amount of CPU cores.

On a 4 core CPU this means that any value between 0 and 24% will fall back on the "Use at most N of the processors" value, 25% - 49% is 1 core, 50% - 74% is 2 cores, 75% - 99% is 3 cores and 100% is 4 cores. You can calculate what that means for an 8 core (4 core with hyperthreading).

In the actual calculation time this doesn't matter much, as each core will only run one task.

Now the question: Why did you buy such a heavy machine, if you want to hamper it so much? Why didn't you go for an i3 or i5? The i7s have always been a hot series, ever since their first generation. Now with the 3rd generation, there are enough articles out there that you can research --just fill into Google "i7 hot" without the quotes-- that show that the CPU will get hot and therefore needs ample adequate cooling. And that it will get hot when you run 'normal' things as well, such as 3D screen savers, or playing games.
____________
Jord

Fighting for the correct use of the apostrophe, together with Weird Al Yankovic

mikeymike
Send message
Joined: 4 Jan 11
Posts: 3
Credit: 137,988
RAC: 23
United States
Message 1507838 - Posted: 24 Apr 2014, 0:49:41 UTC

This, maybe not the correct spot, so. Just wondering, why does Astropulse have less completion time while computing time is 4x to 5x more than say, Seti at Home?

OzzFan
Volunteer tester
Avatar
Send message
Joined: 9 Apr 02
Posts: 13632
Credit: 31,155,765
RAC: 20,210
United States
Message 1507851 - Posted: 24 Apr 2014, 1:18:33 UTC - in response to Message 1507838.

Your question has confused me. Are you asking why AstroPulse takes so long, or why it takes so short?

mikeymike
Send message
Joined: 4 Jan 11
Posts: 3
Credit: 137,988
RAC: 23
United States
Message 1508826 - Posted: 26 Apr 2014, 14:19:15 UTC - in response to Message 1507851.

Let's say; Astropulse estimates 45hrs of computer time and 30 days to complete. Seti at home estimates 9hrs of computer time and 60 days to complete. Why doesn't Astropulse allow 300 days to complete the task?

OzzFan
Volunteer tester
Avatar
Send message
Joined: 9 Apr 02
Posts: 13632
Credit: 31,155,765
RAC: 20,210
United States
Message 1508839 - Posted: 26 Apr 2014, 15:18:23 UTC - in response to Message 1508826.

I'm honestly not sure what mechanism or algorithm determines the deadlines; however, I'm not seeing 60 days to complete for my SETI@home tasks. Most of mine are three weeks out.

I can tell you that 300 days to complete an AstroPulse task would be nearly a year and would have a lot of credit hunters up in arms. Most of them want shorter deadlines so they can get credit faster.

I can also tell you that since we are not dealing with time-sensitive information, the deadlines are largely arbitrary. They're mostly used just to ensure that if a workunit isn't completed after a given amount of time, that workunit will automatically be re-distributed to another computer to make sure the work is done.

Perhaps someone else who knows how the deadlines are determined can explain further.

Profile ZalsterProject donor
Volunteer tester
Avatar
Send message
Joined: 27 May 99
Posts: 826
Credit: 38,830,426
RAC: 187,757
United States
Message 1508840 - Posted: 26 Apr 2014, 15:19:02 UTC - in response to Message 1508826.

Ok, that just confused me even more. Where are you getting your numbers from? When you look at the Boinc Task Manager (I'm assuming you changed it to the Advanced view), you should see the different work types listed there. I'm guessing you are seeing there that it says 45 hours estimated to complete and the deadline as 30 days? The 45 is an average of how long it takes your computer to complete 1 astropulse. After some 20 astropulses, seti gets a better idea of how long it takes to complete one (assuming you leave your computer on all the time and allow it to do nothing but the crunching) otherwise, that number is going to vary wildly depending on your usage of the computer. Why not 300 days? There has to be a limit, otherwise a lot of work units would never come back and the backlog of workunits that needed to be resent would be even greater than it currently is. The 30 days allows for both users (you and your wingman) to complete the work unit and if need be for it to be sent to a 3, 4 or even 5 person to run the data.


Where you are getting 9 hrs and 60 days from? Is it from somewhere in another post or somewhere in the "about section" of Seti@home?

mikeymike
Send message
Joined: 4 Jan 11
Posts: 3
Credit: 137,988
RAC: 23
United States
Message 1508858 - Posted: 26 Apr 2014, 16:54:17 UTC - in response to Message 1508840.

Thanks. When I open Bionic Manager, where it shows tasks. Seti@home completion date of 06/14/14 and I started that task about 1 week ago. ok, not exactly 60 days but pretty close. I just thought, if that task has 5 times less computing time than an AstroPulse task, the 300 days is just a ratio compared to Seti@home. It seemed like 30 days maybe getting a little rammy.

Questions and Answers : Wish list : Astropulse & other long computing tasks

Copyright © 2014 University of California