News:

Follow BoincTasks on Twitter Facebook        Visit our website here.
BoincTasks cloud login is working again

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - BobCat13

#1
Questions / Re: CPU% - 2 things I don't understand
February 15, 2016, 03:28:06 AM
Quote from: fred on February 15, 2016, 03:12:53 AM
Quote from: BobCat13 on February 15, 2016, 03:00:18 AM
Thanks, set that to 1 and restarted BoincTasks but CPU% is still capped at 100.
OK I see what you mean, but can you actually see that 2 cores are used.
What does the BOINC manager report.
BOINC Manager reports the task is using 2 cpus as does BoincTasks if I enable the Use column.  I was just hoping to see the exact percentage of CPU time/Elapsed time to make it easier when testing to see if it is more efficient to run these tasks with 2 cores, 3 cores, or 4 cores on a quad core machine.
#2
Questions / Re: CPU% - 2 things I don't understand
February 15, 2016, 03:00:18 AM
Quote from: fred on February 15, 2016, 01:24:34 AM
C:\Program Files\eFMer\BoincTasks\examples read the config.xml comment.
The config.xml should contain.
<config>
   <options>
      <no_cleanup>   1</no_cleanup>
   </options>
</config>

no_cleanup set to 1 should do the trick.
Thanks, set that to 1 and restarted BoincTasks but CPU% is still capped at 100.

Here is the log:
14 February 2016 - 21:44:53 BoincTasks version: 1.69
14 February 2016 - 21:44:53 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
14 February 2016 - 21:44:54 config.xml ---- no_cleanup
14 February 2016 - 21:44:54 Maximum number of computers: Unlimited
14 February 2016 - 21:44:54 Computers ---- Green , IP: localhost
14 February 2016 - 21:44:54 Computers ---- Blue , IP: 192.x.x.x
14 February 2016 - 21:44:54 Computers ---- Orange , IP: 192.x.x.x
14 February 2016 - 21:45:07 Connect ---- Connected to: Host: Orange, IP: 192.x.x.x, Port: 31416, BOINC Version: 7.6.23
14 February 2016 - 21:45:07 Connect ---- Connected to: Host: Green, IP: localhost, Port: 31416, BOINC Version: 7.6.22
14 February 2016 - 21:45:07 Connect ---- Connected to: Host: Blue, IP: 192.x.x.x, Port: 31416, BOINC Version: 7.4.41

And here are the columns shown in the Tasks tab for the multithreaded task:
Computer: Blue
Project: Cosmology@Home
Application: 1.02 planck_param_sims (vbox64_mt)
Task Name: planck_param_sims_2_2250_379_0
Elapsed Time: 00:12:46 (00:24:52)
Progress %: 10.600
Time Left: 00:41:12
Deadline: 2-20-2016 5:38:55 PM
Status: Running
Checkpoint: [1] 00:04:38
CPU %: 100.000   
#3
Questions / Re: CPU% - 2 things I don't understand
February 15, 2016, 01:10:36 AM
Quote from: fred on September 29, 2015, 04:25:48 PM
BoincTasks should limit to 100% unless you override it.
How can this override be accomplished?  On multithreaded apps, I would like to see the exact percentage, i.e. 190% for an app using 2 cpus instead of being capped at 100%.
#4
Questions / Re: Must be missing something basic
December 09, 2015, 03:54:54 AM
Don't use the allow_remote_gui_rpc in cc_config file.  Remove that option completely from cc_config.xml.

Add the Win box's IP to remote_hosts.cfg and create a password in gui_rpc_auth.cfg.  If the client was installed from the repository, these files will be in etc/boinc-client as the ones in /var/lib/boinc-client are just links not to be edited.
#5
Wish List / Re: New Rules to add
March 04, 2015, 08:14:17 PM
Under Event, it would be nice to have Suspend network and Resume network. 

There are times when some rules are triggered, that I would like to suspend or resume the core client's internet access.  At present, I am doing that by launching a .bat file for the affected machine.  Only problem is, this requires a separate rule and .bat file for each machine since I don't want to suspend or resume network on machines that didn't trigger the rule.
#6
Running BT 1.37 on Localhost

Localhost (WinXP SP3 32-bit, ver. 6.12.43)

Project Orbit@home
CPU backoff time   7-25-2012 6:42:04 AM
Backoff Interval   24:00:00
   

Remote Linux (Lubuntu 11.10, ver. 7.0.27)

Project Rioja Science
CPU backoff time   373105:27:39
Backoff Interval   00:10:00

The 373105 is hours since January 1, 1970, in case that helps.  Fred E.'s 15545 is the number of days since January 1, 1970.

#7
Beta Testing / Re: BT-1.30 new bugs?
February 16, 2012, 02:55:40 AM
Quote from: Tex1954 on February 15, 2012, 10:11:59 PM
1) No matter the settings, I can't ever right-click on a project or task and get "Properties".  BT-1.25 the same problem.
My problem is a little different from Tex1954's on the properties dialog.  I can get the Properties dialogs to display, but on the Project Properties if a project has negative short/long debt, all I see is the - (minus) character but no numbers after it.

Running boinc client 6.12.43 on Windows XP, tried both BoincTasks 1.21 & 1.30.

Here is a screenshot of the Properties from both BT and BOINC Manager.  Project Properties
#8
Beta Testing / Re: BT 1.17
August 19, 2011, 03:42:47 PM
All of the % bars are completely filled in no matter what percentage is used.

Projects: Share %, Tasks: Progress % and CPU %, Transfers: Progress %

Here are 2 screenshots to compare in Tasks view:  one for v1.16 and one for v1.17

v1.16

v1.17
#9
Beta Testing / Re: BT 0.90
November 27, 2010, 11:23:05 PM
While trying to click on BOINC preference (under Extra), I accidentally clicked on BOINC proxy settings causing BT to crash.  BT is attached to localhost and one remote host.  I tried several more times just to check that it wasn't a one time crash.  Four tries while attached to local & remote all crashed, as did four tries while attached to local only.  Running XP Pro SP3 32-bit on the localhost.
#10
Beta Testing / Re: BT 0.71
August 22, 2010, 10:09:58 PM
Three computers are monitored by BT, let's call them 1 (localhost), 2 and 3 (both remote).  After switching to the Computers tab and unchecking one of the remote boxes (#2), then switching back to the Tasks tab, the Extra --> Allow network communication has the following listed:  1, 3, 1, 2, 3.

The first 1 and 3 work, but highlighting any of the 1, 2, or 3 below those causes BT to lockup and the machine becomes unusable until BT is terminated.  I have waited over 5 minutes and BT does not crash and restart, it just stays locked up.