| log in |
|
1)
Message boards :
Number crunching :
Report Deadlines
(Message 1508)
Posted 15 Feb 2019 by additude Hi Jim1348, I appreciate your feedback. What I read from what you've told me is that an extended task due date wouldn't affect you or your process one way or the other. Extended or not, you just keep on doing what you do and remain completely unaffected one way or the other so it really makes no difference in the process you follow, or your results. That's the beauty of it. If you weren't informed of it, you wouldn't even be aware of it in your process. One thing I would not be in total agreement with you about is when you say "It is up to the projects to decide how best to maximize their output". I would remind you that there are numerous configuration settings used for personalizing the BOINC process to suit a users needs and requirements for efficiency and maximizing thru-put. BOINC has also detailed a few technical studies focusing on BOINC efficiencies, report deadlines being a part of those trials. From my experience, extending a task due date has more benefit than detriment. Especially when it has none, or almost zero ( I don't know of any ), impact on current users or even current tasks in process. It's as simple as trial and error. There is no harm to try, it is simple to implement and it is just as simple to reset if something doesn't work out. |
|
2)
Message boards :
Number crunching :
Report Deadlines
(Message 1506)
Posted 15 Feb 2019 by additude Agreed Jim1348 if you're a single project researcher, but there are more projects than just one; and Boinc and the account managers are all designed and equipped to run multiple projects simultaneously. As far as "short turnarounds" go in relation to due dates, that's technically an irrelevant consideration because the task gets completed when the task gets completed. If the "due date" is at 10 days and the task is completed in 1 day, then so be it. Move on to the next task, then the next... The due date has no relevancy in that respect. |
|
3)
Message boards :
Number crunching :
Report Deadlines
(Message 1505)
Posted 15 Feb 2019 by additude I just configured TN-Grid to allow-more-work and it downloaded ~50 Tasks for each of 4 machines, due in 5 days.....which means that for each machine I have 960 / 10 = 96 hours of available processing time for TN over the course of 5 days. I have TN-Grid set to 10% of two projects, 3day buffer +2days. So I feel that this is over-extended so I would need to adjust the buffer to 1day +0 days...But that will affect my other project because this is a BOINC global setting. I also have the global_prefs_override.xml file set to 5 days. So I will have to disable global_prefs_override.xml... I think this is going to trigger the (EDF) priority in Boinc and I will lose all processing of my second project even though it's set to 90% This is just an example of the problem I am experiencing because of the 5 day report deadline. |
|
4)
Message boards :
Number crunching :
Weird hosts
(Message 1502)
Posted 15 Feb 2019 by additude Hello, There is no available resource on the pool for an individual pool user to locate another pool user by computer id. Contact Brian at admin@grcpool.com . He will respond as quickly as he can. He responds to critical issues fairly quickly. Try putting something spiffy in the Subject like "From Admin at TN-Grid" to get his attention. |
|
5)
Message boards :
Number crunching :
Report Deadlines
(Message 1501)
Posted 15 Feb 2019 by additude Hi, I've been doing this for quite awhile and although I haven't done TN-Grid until recently, I do run multiple projects on one machine and when running more than one project there has to be a harmonious balance between them. Most other projects are 10 days to 14 days on report deadlines. Case 1. I see some WU's can take 20 hours to complete, while some are 5 or 6 hours. Well, 5 hours is 1 hour a day of processing over 5 days. 20 is 4 hours a day. A percentage of folks don't run dedicated machines like I do and they don't leave their machines powered on 24/7. These folks are being excluded from the project because they can't meet the imposed report deadlines. I have some completed WU's that are "Completed, too late to validate" and that means I spent 15 hours of my time for nothing. BOINC refers to this as "Waste". If that's going to be the case then I am forced to move on to a different project because I am forfeiting any incentive to process these WU's. Case 2. BOINC Manager has it's own Priority Algorithm (EDF) that prioritizes WU's by due dates. If I'm processing two projects at any processing percentage between them, 50/50, 1/99, etc. and one project has a 14 day due date and the other a 5 day due date then you can see how BOINC will tend to favor the 5 day WU's and override any settings I have for split time processing between projects. Even if I have it tilted strongly in favor of the other project, BOINC will override that for a due date priority. It's not just about setting the cache size to 1. That is defeating the purpose and need of having a WU cache at all to compensate for connection problems, etc. It is proven by BOINC that a 1 cache value increase "Waste" dramatically. TN-Grid supplies WU's that the community processes and returns for an incentive. That incentive, as simple as it is, is a numerical value, status and a badge signifying accomplishment. TN-Grid needs results as soon as it can get them all returned. It would be great if every BOINCer had TN-Grid project on their machines, but it is not that way. A 5 day due date is a further restriction that limits the number of WU's that can be processed by everyone attached to the project. Assigned tasks that do not get processed need to be re-issued. You may think that a 5 day due date provides a improved project performance, quicker turn-around, but that in itself is limiting, a restriction that may be causing extended results reporting by restricting to the number of users that have the "means" to process a task in 5 days or less...and those that don't participate because they don't even want to deal with it. Universe, Asteroids, Seti - all 10-14 days. There is valid logic behind that number. In reality, a minimal report deadline is directly comparable to a minimal cache size. The lesser they are the higher the increased value of "Waste". I recommend setting report deadline dates to 10 days and monitoring this to see what scheduling and results performance does. It might take 4 weeks or a bit longer to balance and get into a rhythm. But you should continually see improvements in efficiency. Just think about it. |
|
6)
Message boards :
Number crunching :
Report Deadlines
(Message 1499)
Posted 14 Feb 2019 by additude Yea, Thanks. I ended up doing a nomorework and then I had to suspend TN for 24 hours... I put my TN settings to 10% and 2 days work. Once I get a balance between projects I'll reinstate everything... Thanks again. -Wes |
|
7)
Message boards :
Number crunching :
TN WU's failure and error rates
(Message 1498)
Posted 14 Feb 2019 by additude Hi, well I have had to back off TN Grid on them for a little while because of the report deadlines of the TN-Grid tasks...which is 5 days. That's the shortest deadlines I've seen. I have another project that I am running on them and the TN-Grid tasks deadlines cause the BOINC priorities to automatically give TN priority. These are Odroid XU4's. You can google a search to find out where to purchase them. Odroid.com is pretty much as good as any other once price and shipping is considered. I'm using mostly Micro SSD's on them. BOINC is not drive intense so an emmc is a bit of overkill for BOINC. I am running Ubuntu 16.04 on most, 18.04 on others. What you see here is a fraction of my setup. The majority are in grcpool. There are OS images on the Odroid website to download and use SD Card Formatter and Win32 Disk Imager to write the .img Then I run headless, so I use the "minimal" image. Then it's a matter of updating them, assigning hostname, editing the /etc/hosts file and installing BOINC. Then it's all command line work using boinccmd commands. It's a bit more involved than your normal Windows GUI install... |
|
8)
Message boards :
Number crunching :
TN WU's failure and error rates
(Message 1496)
Posted 11 Feb 2019 by additude I want to give a heads up and report that on my ARM Odroid XU4's I am realizing about a 10% error/failure rate on my processed tasks. I have several exact-same machines and TN is behaving the same on all of them including the ones that I have in the GRC Pool. http://gene.disi.unitn.it/test/show_host_detail.php?hostid=44191 -Wes |
|
9)
Message boards :
Number crunching :
Report Deadlines
(Message 1494)
Posted 10 Feb 2019 by additude Cool....I'm hoping it will iron itself out... But a 5 day WU is a pretty tight schedule, I think especially on machines that are not dedicated. Thanks. |
|
10)
Message boards :
Number crunching :
Report Deadlines
(Message 1492)
Posted 9 Feb 2019 by additude A few days ago (6 days) I turned 4 of my ARM machines over to crunch outside my team and I am running Ubuntu headless. Clean fresh install, updated, installed BOINC and attached to TN-GRID project. I also attached to Universe Project. I have downloaded WU's from both, but my machines will only run TN-GRID WU's and I believe the reason has something to do with report deadlines. I'm monitoring today and I every TN-GRID WU I'm processing has a due date of today, Feb. 9th. If due dates are in local time, I finished one WU less that 30 minutes before it's due time. If the time is in GMT, I'm 4 hrs and 30 minutes late. So far I've done 200 WU's in 6 days... so there's no slack time on my part..... I haven't ran a single Universe WU yeat because of report deadline precidence of TN-GRID WU's.... I think.... I'm just wondering if there is any sensible explanaition... Thanks. This is a link to WU's I received on 4th...due on the 9th.... http://gene.disi.unitn.it/test/results.php?userid=2295&offset=260&show_names=0&state=0&appid= Due in 5 days.... That with other WU's I have 229 in progress...... |