Your thread's becoming 'da bomb' for spammers lately. Warning to all would-be spammers posting after this: your post will be deleted and your account will be banished immediately. No need to post your shit here, it'll be gone before you know it.

---

Fred,

Of late started noticing ** that BT was using quite a bit of CPU time, probably around 0.96 but could be earlier. Left BT 1.02 up overnight (My crunchers work off line, so normally don't), and in 9 hours wall-time, it showed this morning to have use > 2 hours on 1 core. That would work to take 5.5 hours per day.

cheers

** Looked when observing that the daily crunch time dropped quite a bit for sources eating time.

Fred,

Of late started noticing ** that BT was using quite a bit of CPU time, probably around 0.96 but could be earlier.

Should not do that. In the 0.05 range on a single computer.
But, close BT when not in use -> [X] -> move to the tray.
In the History setting check "Smart mode"
Set the "Maximum Update time" to 120 seconds.

When you have a lot of computers you may consider disabling the history.

---

TThrottle The way to control your CPU and GPU temperature.
BoincTasks The best view of BOINC.
My other activities

Been run as "But, close BT when not in use -> [X] -> move to the tray.", and will give your other settings a try. Just few computer. Though the Wlan is 270Mb measured, when changing remote prefs, nothing else, BT seems to loose connection for a fraction, blanking the task list, holding some 50 tasks, then coming back. The log then says that the changes were applied, but when looking in the actual pref, they appear to show the state prior to. Maybe it's straining too much for remotes, so will disconnect them for a bit if the change tips don't work out.

--//--

Update: Seems that the History screen is being updated every second no matter the setting, 120, 119..., pulsing then at 15% load, which is eating the CPU time [v 1.03]

Just noticed also that though properly exiting and the tray icon disappearing, the boinctasks.exe remains memory resident and continues to pulse this 15% load every second. Starting BT does not say that a copy is already running and loads properly.

Also have a strange bug which only manifests on W7-32, client 6.10.25 and 26, don't know if this was a problem with previous clients. Cannot suspend a task through BT, but it works via the standard BM. Tasks that are waiting to run or running can be suspended. When selecting a "running" or "waiting to run" task and combine this with a Ready to Start task (RtS), then the RtS will suspend, but suspect that is because the task is run for a fraction of a second before suspending during the multi-task selection suspend. Reversing to select a suspended tasks not yet started does not work, but when already started it does. The oddest part is, from W7-64 and remotely suspending and resuming to this W7-32 host not yet started tasks suspending works fine. Also from W7-32 remote controlling a 64 bit client works fine with BT.

cheers

Update: Seems that the History screen is being updated every second no matter the setting, 120, 119..., pulsing then at 15% load, which is eating the CPU time [v 1.03]

Was there any running task at (or near to) 100% progress at the moment (err, during the high CPU load and rapid History refreshing)? Was BT's GUI also very unresponsive during this?

Also have a strange bug which only manifests on W7-32, client 6.10.25 and 26, don't know if this was a problem with previous clients. Cannot suspend a task through BT, but it works via the standard BM. Tasks that are waiting to run or running can be suspended. When selecting a "running" or "waiting to run" task and combine this with a Ready to Start task (RtS), then the RtS will suspend, but suspect that is because the task is run for a fraction of a second before suspending during the multi-task selection suspend. Reversing to select a suspended tasks not yet started does not work, but when already started it does.

I've reported the same problem 4 days ago: while BT was in such busy mode, it was able to suspend/resume any of the running or ready-to-run tasks as usual, but it (sometimes?) could not modify the suspend/resume state of the not-yet-started ("ready to start") tasks (I've tried to restart BT a couple of times, but no joy - BOINC Manager had to help.)

Peter

Well, there is that infinite QCN task at 9519%. No idea, but feel it's something to do with BT not properly loading/unloading. Same version on W7-64 unloads completely. The BT GUI responsiveness is good enough for me not to notice and lagging.

edit: Ha, suspended the QCN task and the refreshing immediately switched to 30 seconds that I'd changed it to. Then when resuming the task history kept updating at 30 second intervals for a little, then reverted to the 1 second order. For this glorious occasion, aborted the QCN task and fetched a new one. At 0.1%, the history updating has held 30 seconds.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Well, there is that infinite QCN task at 9519%. No idea, but feel it's something to do with BT not properly loading/unloading. Same version on W7-64 unloads completely. The BT GUI responsiveness is good enough for me not to notice and lagging.

The problem is a history that updates to quickly, I will change that in the next version.

Go to BT settings and remove the check at "Smart mode".
This setting only works with projects that behave properly.
Not with projects that are >= 100% or have an invalid time left.

The problem with the 32 bit machine may be an access/password problem.
In the BT log check "Enable debug mode"
Restart BT and check the log for: localhost get local password
See if the password that is read back is the correct one.

Another thing that may cause this is that you have removed a critical column.
Like computer, project, name.

---

TThrottle The way to control your CPU and GPU temperature.
BoincTasks The best view of BOINC.
My other activities

OK, found the box in the Show Log window and restarted BT. This was recorded... some stuff changed for YKW reasons and no line reading out a password. The connections per the Computer tab are all fine, and when clicking the password field, the correct pw is shown.

24 mei 2011 - 17:11:46 Logging ---- Start debug mode
24 mei 2011 - 17:11:46 Logging ---- fileonly
24 mei 2011 - 17:11:46
...
24 mag 2011 - 17:11:46 Main ---- BoincTasks Version: 1.03
24 mag 2011 - 17:11:47 GetLocalDirectory ---- C:\Program Files\eFMer\BoincTasks
24 mag 2011 - 17:11:48 BoincTasks version: 1.03
24 mag 2011 - 17:11:48 Maximum number of computers: 60
24 mag 2011 - 17:11:48 Computers ---- xxxxxxxx , localhost
24 mag 2011 - 17:11:48 GetLocalDirectory ---- C:\Program Files\eFMer\BoincTasks
24 mag 2011 - 17:11:48 GetLocalDirectory ---- C:\Program Files\eFMer\BoincTasks
24 mag 2011 - 17:11:48 Connect ---- Connected to: Host: localhost, xxxxxxxx, Port: 31416, BOINC Version: 6.12.25
24 mag 2011 - 17:11:49 Html create ---- ERROR: Unable to find: C:\Users\memememe\AppData\Roaming\eFMer\BoincTasks\html\tasks_template.html
24 mag 2011 - 17:11:49 Start Ftp ---- ERROR: Unable to start: C:\Users\memememe\AppData\Roaming\eFMer\BoincTasks\html\ftp.bat
24 mag 2011 - 17:11:49 GetLocalDirectory ---- C:\Program Files\eFMer\BoincTasks
24 mag 2011 - 17:12:16 Memory ----

I'm starting BT in admin mode so always get the UAC screen, by choice. BOINC is a "PAE/Allow All Users" install.

edit: Oh and the RtS task suspending and resuming now works fine. Maybe a race condition after all due the continuous history updating. And low and behold, remote preferences updating now also works to the Linux client AND BT now unloads completely... lots of knock on effects there were due the now exitus QCN task that was > 100% :D

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

24 mag 2011 - 17:11:49 Html create ---- ERROR: Unable to find: C:\Users\memememe\AppData\Roaming\eFMer\BoincTasks\html\tasks_template.html

This is a strange error. Did you change the default xml folder?

I'm starting BT in admin mode so always get the UAC screen

Why? There should be no need to.

---

TThrottle The way to control your CPU and GPU temperature.
BoincTasks The best view of BOINC.
My other activities

Well, there is that infinite QCN task at 9519%.
[...]
edit: Ha, suspended the QCN task and the refreshing immediately switched to 30 seconds that I'd changed it to. Then when resuming the task history kept updating at 30 second intervals for a little, then reverted to the 1 second order.

Yes, the trigger is a running task at or over 100% progress.
When a suspended task is resumed, it takes a while for BT to get into this state.

Peter

Well, there is that infinite QCN task at 9519%.

The problem is a history that updates to quickly, I will change that in the next version.

Go to BT settings and remove the check at "Smart mode".
This setting only works with projects that behave properly.
Not with projects that are >= 100% or have an invalid time left.

I have even tried this (just at the moment I have a DNETC task, running 3/4 hour at 100% with no remaining time estimate). The "Smart mode" chackbox has no influence on BT's behavior!

Peter

Not aware of me ever changing anything on BT installations. Navigated to that place. Looking at some sub-folder timestamps it for sure is the location that BT is reading/writing too such as the history, a set of 3 for each device. Neither tasks_template.html nor ftp.bat are anywhere to be found. Starting BT with admin makes no difference... those 2 files remain lost.

Not aware of me ever changing anything on BT installations. Navigated to that place. Looking at some sub-folder timestamps it for sure is the location that BT is reading/writing too such as the history, a set of 3 for each device. Neither tasks_template.html nor ftp.bat are anywhere to be found. Starting BT with admin makes no difference... those 2 files remain lost.

To remove the warning go to BT Settings -> WWW and remove the check at Enable WWW Updates.

You can read this when you want to enable this feature.

http://www.efmer.eu/forum_tt/index.php?board=27.0

3 for each device
BT makes a rotation copy of 3 files, only writes one at a time and renames the others.
The purpose is to ensure your history is never lost.
When the first file gets corrupted it takes copy 2 or 3.
When Window closes it's not always very controlled and BT may be in the middle of a write that can't be completed.

---

TThrottle The way to control your CPU and GPU temperature.
BoincTasks The best view of BOINC.
My other activities

OK, thanks Fred. Looks to be running smoothly now, never having had the urge to have info send to me smartphone.

Per Process Explorer 31 seconds were used since last launch some 80 minutes ago. With all the interface activity an excellent number.

--//--

Update: 18:30 hours later 8:50 minutes were logged whilst during that time BT had been sitting for several hours with expanded window with v 1.03.

Did catch some hour ago that a second copy had been running with nearly 9 minutes used that somehow managed itself to load this morning. Forgot to look who the owner was of the process. Momentarily, if hitting the launch icon on the start bar, the window of the active instance is expanded from the systray. No warning as seen in past where it says that a copy of BT is already running.

cheers

1.04 May 2011
New: A rule that triggers when a computer or all computers loose connection.
New: History: A minimum update time in the settings dialog. Default was 2 seconds, now 4 seconds.
New: Rules logging: Logs the moment a rule is no longer active and is removed.
Changed: Everywhere (Mayor change) , changed the type of data storage list used. Will probably effect the History most, let me know if you notice speed differences. sks/History: refresh, set the new time after the screen is updated and not before, to avoid too frequent updates.
Changed: Tasks/History: Updating... now Updating 3, with counter when > 3 seconds.
Changed: Transfers: now shows 2 digits at Size and Speed.
Fixed: Tasks: Deadline shown as time left, past the deadline was shown as ??, now shows negative time -12:33:07.
Fixed: Transfers: The size/speed wasn't correct, slightly too high.
Fixed: Add project didn't work on a computer without projects. Extra fall back, search for any connected computer and use the first one.
Fixed: The /LOCATION flag isn't working.

---

TThrottle The way to control your CPU and GPU temperature.
BoincTasks The best view of BOINC.
My other activities

1.05 June 2011
New: BoincTasks new version in Notices.
New: Notices: A expand/collapse icon to hide text and a delete icon to delete a subject.
Changed: Notices, a complete redesign. Now uses a notices.xml file, to store notices specific data. This will better handle notices over computers.
Changed: Check for a new version after 1 minute, to ensure there is an Internet connection.
Changed: Transfers: Status text Retry in: into Upload pending (Retry in) or Download pending (Retry in).
Changed: notices_template.html.
Fixed: The history files where unnecessary large, due to the repeating of the computer name in the file.

---

TThrottle The way to control your CPU and GPU temperature.
BoincTasks The best view of BOINC.
My other activities

Fixed: The history files where unnecessary large, due to the repeating of the computer name in the file.

Don't know if others have experienced this but on upgrading to 1.05 and looking in the history, all but the last 24 hours was gone for local and remote hosts. Checking BT settings, the days were still on 365 to keep. After, the history held all new results not wiping the > 24 hours.

--//--

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Fixed: The history files where unnecessary large, due to the repeating of the computer name in the file.

These large computer names appeared sometimes in the last 3 weeks, most probably with BT 1.04 update.

Don't know if others have experienced this but on upgrading to 1.05 and looking in the history, all but the last 24 hours was gone for local and remote hosts. Checking BT settings, the days were still on 365 to keep. After, the history held all new results not wiping the > 24 hours.

Happened to me on one computer with BT 1.03->1.04 transition. This means that the bug is still available in 1.05 :-(

On two other machines I'm possibly missing some historical data older than a couple of months, but I have no evidence because of having no backups. But I'm suspecting the remaining historical data being "thinned" - I've observed this on one machine, when shortening the "Remove history after ... days" value step-by-step.

Peter