Posts by Ingleside

1) Message boards : Questions and problems : Do all lines Read In from cc_config.xml immediately take effect? (Message 32719) Posted 11 May 2010 by Ingleside Post: Sorry, I was posting in a hurry while trying to load up for a weekend away. I just wanted to alert readers that ncpus was an instant-acting, rather than deferred, option - Gundolf wasn't sure, and had pointed in the opposite direction. Just had time to run the test and post a single copy of the full results :-( Except if set to default, -1, that is only taking effect after client re-start.
2) Message boards : BOINC client : rsc_memory_bound still in effect? (Message 27439) Posted 16 Sep 2009 by Ingleside Post: Not only related to the core client ... Does "<rsc_memory_bound>" still do something? It's used by the scheduling-server when deciding if host can handle the task or not. If wu.rsc_memory_bound > usable_ram, it won't be sent to computer, there usable_ram is the max of users active and idle memory-limits, or computers installed memory in case of really old client.
3) Message boards : BOINC Manager : Ready to report? (Message 12032) Posted 10 Aug 2007 by Ingleside Post: Hm, what's the Work Buffer setting? Where can I find it? I have version 5.8.15... You're running WCG, right? If so, it's called "Connect to network about every N days", and is under Device Manager/profiles
4) Message boards : BOINC Manager : Ready to report? (Message 12030) Posted 10 Aug 2007 by Ingleside Post: Edit: When I pressed Update the two tasks labeled "Ready to report" dissappeared from the Tasks list. But still, it says under project status: communication deffered? To not over-burden the Server with connections, there's always a small delay, normally between a couple seconds and 10 minutes, before client is allowed to connect again. The client will display this deferral, even there's no current problems and even if there's no current reason a new connection is needed.
5) Message boards : BOINC Manager : Ready to report? (Message 12029) Posted 10 Aug 2007 by Ingleside Post: 3. The Result has been in the Ready to Report status longer than the Work Buffer setting. #3 is deprecated in v5.10.14, instead you'll have new rule of reporting after 24 hours. There's also a rule about "net_status.have_sporadic_connection", but I'm unsure if this is only for dialup-users or... See BOINC-Wiki
6) Message boards : BOINC client : Request: Automatic Purge Function (Message 10274) Posted 15 May 2007 by Ingleside Post: Can you clarify this pls? Does the client pick up an xml of WUs that are to be cancelled? How does the client know if the particular task it's running is to be cancelled or not? Or is it only tasks that have expired that can be cancelled? The list of results (if any) to abort is generated by Scheduling-server, and will be included as part of any normal scheduler-reply, as long as project has enabled aborting of results.
7) Message boards : BOINC client : Request: Automatic Purge Function (Message 10252) Posted 14 May 2007 by Ingleside Post: WCG implemented it and created some of the server side code. Recently it send instruction to BOINC clients for a bad batch. It only works on >= 5.8 clients. Think D@H adopted their code. Theoretically servers could send an instruction to clients where work was deemed 'Too Late' or 'No Reply', but thing is, the client has to initiate a server contact. Not heard if the abort feature is being employed to do those. Helps efficiency and lessens frustration if inadvertently one gets completed and zero credit is awarded. WCG had nothing to do with the client-side implementation. Server-side, there was some discussion of tying aborting into the re-issue-functionality to minimize db-server-load, but AFAIK no-one finished this, so WCG made their own server-code and got this added to standard BOINC 05.04.2007 so all projects can choose to enable this. For results past deadline or wu Assimilated, if enabled server sends result_abort_if_not_started, but unfortunately this only works in v5.8.17 or later. result_abort on the other hand works with v5.5.1 or later.
8) Message boards : BOINC client : Request: Automatic Purge Function (Message 10182) Posted 11 May 2007 by Ingleside Post: This is handled by 2 flags: 1; result_abort 2; result_abort_if_not_started As the names implies, #1 will immediately abort result. Intended used if wu cancelled by project or errored-out, meaning result won't be used by project and user won't get any credit for it, and it's therefore a waste of time to continue. #2 will only abort if have never started crunching a result, even if you've only crunched 1 second client won't abort result. Intended used in cases wu has already got "canonical result", meaning result won't be used by project and it's therefore no point to start crunching it. But, since user can still get credit for result, a started result isn't cancelled, since it's no way to know if only a few seconds or a long time left to crunch... Client-side, #1 has been included for nearly a year, since v5.5.1. #2 was added at the same time, but due to a small bug #2 wasn't working before in v5.8.17, meaning for windows-users you need v5.9.xx. Server-side, nothing was done until WCG had a batch of bad wu's in March? 2007, and they programmed this part, and got it incorporated in general BOINC-code in April with some bug-fixes added later... For project to use this, they needs to enable "send_result_abort" in their config-file.

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.