I must admit that the "
Switched, busy..." text in the status bar is killing my patience. I was looking around for any description of this state and the single place whitch mentions it was pretty unrelated
Quote from: archae86 on April 30, 2010, 04:07:33 PM
... the status box (third from right at on the bottom row), which usually says "updating very briefly, then a count-down from 5 seconds to next update, instead said "switched, busy" for a while, perhaps 20 seconds. Then it changed to "updating..."
without any explanation.
Thus the big question from me, Fred: WHAT is happening under the BT's hoods, when it has to keep this message displayed for a long while, exactly each time I enter any tab's page, and if I want to switch from the tab to another one or click anything else prior to finishing this page's update, the clicks are just buffered and buffered and buffered...
Is it necessary to postpone any other GUI activity (like entering any tab or menu or dialog) until this particular one page is refreshed? (Is it because the same thread (as GUI) is waiting for network data?)
What happens when you hit a tab:
1) The "Switch busy" text will be shown.
2) The screen contents will be updated. In other words a request is send to all computers.
But the computer on the other side may be busy handling other previous requests. Or BOINC is busy with something and responds slowly to the RPC requests from BT.
As soon a the new request for a screen update starts the new text will appear.
Could the communication with all possible connected computers and GUI updates be done asynchronously? At least, when I click through 7 different tabs, their pages could be rendered with the last known contents... And when new data comes in, the currently displayed page can be refreshed. The data is anyway coming in continuously, approx. on the predefined intervals.
Quote from: Pepo on September 24, 2010, 08:28:41 PM
Could the communication with all possible connected computers and GUI updates be done asynchronously? At least, when I click through 7 different tabs, their pages could be rendered with the last known contents... And when new data comes in, the currently displayed page can be refreshed. The data is anyway coming in continuously, approx. on the predefined intervals.
I could make an option not to refresh immediately and let the regular interval take over. It will take some time before you get the most recent data but it will not stress the system as it does now.
Quote from: fred on September 25, 2010, 08:58:03 AM
Quote from: Pepo on September 24, 2010, 08:28:41 PM
Could the communication with all possible connected computers and GUI updates be done asynchronously? At least, when I click through 7 different tabs, their pages could be rendered with the last known contents... And when new data comes in, the currently displayed page can be refreshed. The data is anyway coming in continuously, approx. on the predefined intervals.
I could make an option not to refresh immediately and let the regular interval take over. It will take some time before you get the most recent data but it will not stress the system as it does now.
(http://www.efmer.eu/forum_tt/Themes/default/images/post/thumbup.gif) I'm looking forward!
BTW, how old data is displayed on the pages? I was in belief that the complete data is continuously coming in and is parsed and displayed by any page. (At least in case of
Messages it
must be so, because the client keeps only the last 2k, but BT is capable of correctly displaying the whole hundred thousands when displaying Messages after many days. Just the display list creation takes some time ;D and BT possibly has just to check whether the particular client really still adds messages with correctly incremented ID?)
But as I've checked now, each other tab seems to initially display the same data I've seen maybe yesterday evening, and just after successfully getting an update from connected clients, the page is refreshed. Am I (approximately) right? If so, can the pages be first refreshed with some recent data already abroad?
Quote from: Pepo on September 25, 2010, 09:24:30 AM
(http://www.efmer.eu/forum_tt/Themes/default/images/post/thumbup.gif) I'm looking forward!
BTW, how old data is displayed on the pages? I was in belief that the complete data is continuously coming in and is parsed and displayed by any page. (At least in case of Messages it must be so, because the client keeps only the last 2k, but BT is capable of correctly displaying the whole hundred thousands when displaying Messages after many days. Just the display list creation takes some time ;D and BT possibly has just to check whether the particular client really still adds messages with correctly incremented ID?)
But as I've checked now, each other tab seems to initially display the same data I've seen maybe yesterday evening, and just after successfully getting an update from connected clients, the page is refreshed. Am I (approximately) right? If so, can the pages be first refreshed with some recent data already abroad?
It may be a couple of hours old. As the window is closed, there is almost no activity, except the history fetching.
But I'm not sure what causes your problem.
Basically only the Tasks and History tab may take some time to process all the data.
Is there anyone else, who recognizes these problems.
Quote from: fred on September 25, 2010, 10:35:10 AM
Quote from: Pepo on September 25, 2010, 09:24:30 AM
But as I've checked now, each other tab seems to initially display the same data I've seen maybe yesterday evening, and just after successfully getting an update from connected clients, the page is refreshed. Am I (approximately) right? If so, can the pages be first refreshed with some recent data already abroad?
It may be a couple of hours old. As the window is closed, there is almost no activity, except the history fetching.
The data which is necessary to keep the history up-to-date - that's at least the list of active and finished tasks. Is this not enough to refresh the
Tasks tab?
QuoteBut I'm not sure what causes your problem.
Maybe I do not have anything here you'd consider being a problem :D
Kidding... Could you+someone else check the following switch times?
QuoteBasically only the Tasks and History tab may take some time to process all the data.
When I try to check all tabs, I can sequentially click on them. Then it takes approx. 20 seconds for each one (
Computers,
Projects,
Tasks,
Transfers,
Messages,
History) to refresh and switch to another busy one. I have currently 2 hosts defined (localhost + one offline external) and 5 seconds manual refresh rate. There are 38 (12 active) tasks aboard.
The data which is necessary to keep the history up-to-date - that's at least the list of active and finished tasks. Is this not enough to refresh the Tasks tab?
No not nearly.
The refresh on my computers take < 1 second with 4 computers and 6000+ tasks. But that's on a local net.
So probably the remote computer has a slow connection. And what is slow can't become fast, whatever you do.
Quote from: fred on September 25, 2010, 12:54:17 PM
The refresh on my computers take < 1 second with 4 computers and 6000+ tasks. But that's on a local net.
So probably the remote computer has a slow connection. And what is slow can't become fast, whatever you do.
No, my remote computer is off (Status: "Connected, Not connected" or "Not connected", it depends...) and not even on the same network now... and if, then it's 100 Mbit over 5 meter.
That must be something else then than the remote one.
I've tried to restart BT. Now it takes your 1 second ???
Messages? Stack?
I've been watching this thread with interest. I've got 2 remotes plus localhost attached to BT, all on a local 100Mb subnet, with a typical total of 1100~1300 tasks across the population. Even after BT has run continuously for >1week, mostly minimized, I've never seen the Tasks tab take >2sec to refresh (i.e., Switched, busy). So ???
Quote from: jjwhalen on September 26, 2010, 11:07:40 AM
I've been watching this thread with interest. I've got 2 remotes plus localhost attached to BT, all on a local 100Mb subnet, with a typical total of 1100~1300 tasks across the population. Even after BT has run continuously for >1week, mostly minimized, I've never seen the Tasks tab take >2sec to refresh (i.e., Switched, busy). So ???
I seem to recall Pepo saying recently that he's running BOINC 6.11.6/6.11.7 on his hosts. On a hunch I changed my hosts over from 6.10.58 to the β 6.11.7 and now I'm seeing BT behavior very similar to what Pepo describes. It's possible there are incompatibilities in the RPC calls from BT, the XML from the 6.11.x client, or both. What about those
Notices the new client sends to BM, that display on the Notices tab and popup in the notification area? Could they be causing BT's XML parser to choke?
I'll be rolling BOINC back to 6.10.58 pending further dialog on this subject. If you need further testing, Fred, let me know :)
Quote from: jjwhalen on September 26, 2010, 04:34:21 PM
I seem to recall Pepo saying recently that he's running BOINC 6.11.6/6.11.7 on his hosts. On a hunch I changed my hosts over from 6.10.58 to the β 6.11.7 and now I'm seeing BT behavior very similar to what he describes. It's possible there are incompatibilities in the RPC calls from BT, the XML from the 6.11.x client, or both. What about those Notices the new client sends to BM, that display on the Notices tab and popup in the notification area? Could they be causing BT's XML parser to choke?
I'll be rolling BOINC back to 6.10.58 pending further dialog on this subject. If you need further testing, Fred, let me know :)
\Hmm it may be a but in the BOINC software as this is a real beta version.
It's almost impossible to keep up with all the beta's and test them all.
But it may be that things are not quite compatible.
I may install a beta on my development machine to start implementing the Notices.
Quote from: jjwhalen on September 26, 2010, 04:34:21 PM
I seem to recall Pepo saying recently that he's running BOINC 6.11.6/6.11.7 on his hosts. On a hunch I changed my hosts over from 6.10.58 to the β 6.11.7 and now I'm seeing BT behavior very similar to what Pepo describes. It's possible there are incompatibilities in the RPC calls from BT.....
Could off course be. It is not so long ago some change in the RPC handshake broke its communication with BoincView...
BT runs on the machine with 6.11.6. As I've restarted BT, It had no contact to the machine with 6.11.7, the last one was some week ago (Sunday), but I do not remember whether the tabs' slugishness has been ever since, or appeared at some later point.
I'll try to update the machine to 6.11.7 and will see.
Whatever is causing the slowdown in refresh at the BT end survived the rollback to BOINC 6.10.58 (i.e., uninstall of the 6.11.7, install of 6.10.58). It also survived a shutdown/restart of BT, as well as a reboot of all 3 computers. I was forced to uninstall/reinstall BT 0.74 to restore an (apparently) normal refresh cycle. Weird, huh ???
--EDIT--Forgot to mention: I did not see this behavior a few weeks ago when I tried out BOINC 6.11.6 on my hosts for a brief period (this was before 6.11.7 was released for testing purposes). Hmm...
Quote from: jjwhalen on September 26, 2010, 05:58:52 PM
Weird, huh ???
Absolutely! You are outperforming my observations ;D
Quote from: fred on September 25, 2010, 10:35:10 AM
Is there anyone else, who recognizes these problems.
Oh yes, I've been haunted by "Switched, busy..." messages with BT. I currently have 1 external and 2 local machines monitored. (And 4 external that are ticked off in Computers-tab.) Machines can sometimes be slow to respond or even off line. This seems to especially happen when there are machines off line, even if it's one of the local ones.
I could actually just reproduce this as the external machine is off line. When I switch to Transfers-tab, it took a lot of time for the Switched-message to go away and BT to show an empty screen. It's like it's waiting a lot of time to give up on the offl ine machine.. I have only one of my local one selected for display, though. And it seems to have only happened once as now the subsequent switches are fast again.
There's another symptom I have seen that may or may not be related. Sometimes on Tasks-tab I see status line to show "Update in 6 seconds" then "Updating..." then "Update in 5 seconds" then "Updating..." again and then "Update in 4 seconds" followed by "Updating..." until countdown goes to 1 and then starts over. I have set refresh rate to Slow. I think this was associated with constant ~200kB network transfer rate I was seeing while back in BT.. (This was with all machines on line so 5 external were getting lot of traffic targeted to them.)
Quote from: wicked on September 27, 2010, 04:30:08 AM
Quote from: fred on September 25, 2010, 10:35:10 AM
Is there anyone else, who recognizes these problems.
Machines can sometimes be slow to respond or even off line. This seems to especially happen when there are machines off line, even if it's one of the local ones.
I could actually just reproduce this as the external machine is off line. When I switch to Transfers-tab, it took a lot of time for the Switched-message to go away and BT to show an empty screen. It's like it's waiting a lot of time to give up on the offl ine machine.. I have only one of my local one selected for display, though. And it seems to have only happened once as now the subsequent switches are fast again.
BINGO!
Offline - that should be it. As Fred said, upon each tab switch, all machines are contacted again and this could explain my roughly identical wait times (around 20 seconds - probably network communication timeout) on each tab. And my external machine did go off-line...
QuoteI think this was associated with constant ~200kB network transfer rate I was seeing while back in BT.. (This was with all machines on line so 5 external were getting lot of traffic targeted to them.)
This was the reason I was suggesting optional separate refresh rates (http://www.efmer.eu/forum_tt/index.php?topic=261.msg885#msg885) for (especially far remote external) computers (http://www.efmer.eu/forum_tt/index.php?topic=261.msg887#msg887). (I suspect it did not find its way into the wish list :'()
Quote from: Pepo on September 27, 2010, 07:49:12 AM
BINGO! Offline - that should be it. As Fred said, upon each tab switch, all machines are contacted again and this could explain my roughly identical wait times (around 20 seconds - probably network communication timeout) on each tab. And my external machine did go off-line...
I think this was associated with constant ~200kB network transfer rate I was seeing while back in BT.. (This was with all machines on line so 5 external were getting lot of traffic targeted to them.)
This was the reason I was suggesting optional separate refresh rates (http://www.efmer.eu/forum_tt/index.php?topic=261.msg885#msg885) for (especially far remote external) computers (http://www.efmer.eu/forum_tt/index.php?topic=261.msg887#msg887). (I suspect it did not find its way into the wish list :'()
A computer that times out a couple of times is moved to the unconnected list, but there will be a retry when you setup Reconnect everry....
When a computer is in the unconnected list it's no longer in the request for data list.
The separate refresh is difficult to implement as I need the data from all computers at once in the case of the history.
The other tabs shouldn't request that much data except off course the task tab.
Quote from: wicked on September 27, 2010, 04:30:08 AM
Quote from: fred on September 25, 2010, 10:35:10 AM
Is there anyone else, who recognizes these problems.
1) Oh yes, I've been haunted by "Switched, busy..." messages with BT. I currently have 1 external and 2 local machines monitored. (And 4 external that are ticked off in Computers-tab.) Machines can sometimes be slow to respond or even off line. This seems to especially happen when there are machines off line, even if it's one of the local ones.
I could actually just reproduce this as the external machine is off line. When I switch to Transfers-tab, it took a lot of time for the Switched-message to go away and BT to show an empty screen. It's like it's waiting a lot of time to give up on the offl ine machine.. I have only one of my local one selected for display, though. And it seems to have only happened once as now the subsequent switches are fast again.
2) There's another symptom I have seen that may or may not be related. Sometimes on Tasks-tab I see status line to show "Update in 6 seconds" then "Updating..." then "Update in 5 seconds" then "Updating..." again and then "Update in 4 seconds" followed by "Updating..." until countdown goes to 1 and then starts over. I have set refresh rate to Slow. I think this was associated with constant ~200kB network transfer rate I was seeing while back in BT.. (This was with all machines on line so 5 external were getting lot of traffic targeted to them.)
1) When the computer goes off line, there may be some longer delays. The computer has to timeout first. After a couple of times the computer is regarded disconnected and things should go back to normal.
2) The update counter is linked to the last time it refreshed (wall clock) and the number of tasks, the more the slower it gets.
You may see the update of the history refresh. The history refresh is depended on the remaining time and has a maximum of 30 or 1/2 the expected remaining time.
Quote from: Pepo on September 25, 2010, 01:03:13 PM
I've tried to restart BT. Now it takes your 1 second ???
Quote from: Pepo on September 26, 2010, 05:58:26 PM
BT runs on the machine with 6.11.6. As I've restarted BT, It had no contact to the machine with 6.11.7, the last one was some week ago (Sunday), but I do not remember whether the tabs' slugishness has been ever since, or appeared at some later point.
Quote from: Pepo on September 27, 2010, 07:49:12 AM
Quote from: wicked on September 27, 2010, 04:30:08 AM
I could actually just reproduce this as the external machine is off line. When I switch to Transfers-tab, it took a lot of time for the Switched-message to go away and BT to show an empty screen. It's like it's waiting a lot of time to give up on the offl ine machine.. I have only one of my local one selected for display, though. And it seems to have only happened once as now the subsequent switches are fast again.
BINGO! Offline - that should be it. As Fred said, upon each tab switch, all machines are contacted again and this could explain my roughly identical wait times (around 20 seconds - probably network communication timeout) on each tab. And my external machine did go off-line...
Apparently it is not that simple :-\ My BT suddenly needs 5 seconds to switch between any tabs. Suddenly. It did not happen a hour or two ago. The BT had no contact to any other machine with BOINC since the restart yesterday.
???
Quote from: Pepo on September 27, 2010, 10:25:08 AM
My BT suddenly needs 5 seconds to switch between any tabs. Suddenly. It did not happen a hour or two ago. The BT had no contact to any other machine with BOINC since the restart yesterday.
I've enabled the log's Debug mode. Although the machine have had no contact to the remote one for a week and BT was restarted yesterday, the log looks like following:
BT opened on Tasks tab, not touching anything:
27 september 2010 - 12:56:44 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:56:50 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:56:56 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:57:02 hî ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
27 september 2010 - 12:57:02 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:57:10 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:57:16 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:57:22 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:57:31 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:57:36 hî ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
27 september 2010 - 12:57:36 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:57:44 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:57:49 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:57:54 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:57:59 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:58:04 hî ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
27 september 2010 - 12:58:04 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 12:58:07 hî ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
27 september 2010 - 12:58:14 Vetroplach, Connect ---- Invalid Socket
BT minimized to tray:
27 september 2010 - 13:00:40 hî ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
27 september 2010 - 13:03:12 hî ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
27 september 2010 - 13:05:44 hî ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
BT just restored - opened on Tasks tab, again not touching anything:
27 september 2010 - 13:07:00 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 13:07:04 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 13:07:09 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 13:07:14 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 13:07:21 hî ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
27 september 2010 - 13:07:21 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 13:07:28 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 13:07:33 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 13:07:38 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 13:07:43 Vetroplach, Connect ---- Invalid Socket
27 september 2010 - 13:07:49 hî ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
27 september 2010 - 13:07:49 Vetroplach, Connect ---- Invalid Socket
Apparently BT is constantly trying to reconnect the remote machine. (It's name is not defined by IP, but Win machine name.)
When things become slow, try removing the check at "Connect to TThrottle" in the General tab.
Quote from: fred on September 27, 2010, 12:00:58 PM
When things become slow, try removing the check at "Connect to TThrottle" in the General tab.
I've updated to BT 0.75 some hour and half ago. Just now the tabs switching takes consistent 2 seconds. Toggling "Connect to TThrottle" makes no difference. Debug Log looks pretty the same.
Quote from: Pepo on September 27, 2010, 12:33:24 PM
Quote from: fred on September 27, 2010, 12:00:58 PM
When things become slow, try removing the check at "Connect to TThrottle" in the General tab.
I've updated to BT 0.75 some hour and half ago. Just now the tabs switching takes consistent 2 seconds. Toggling "Connect to TThrottle" makes no difference. Debug Log looks pretty the same.
But do you have the reconnect ever xx second set.
Quote from: fred on September 27, 2010, 12:39:18 PM
Quote from: Pepo on September 27, 2010, 12:33:24 PM
Quote from: fred on September 27, 2010, 12:00:58 PM
When things become slow, try removing the check at "Connect to TThrottle" in the General tab.
I've updated to BT 0.75 some hour and half ago. Just now the tabs switching takes consistent 2 seconds. Toggling "Connect to TThrottle" makes no difference. Debug Log looks pretty the same.
But do you have the reconnect ever xx second set.
Yes, at 710 sec.
Now the delay is around 1.5 sec.
For the next version, I will not request temperatures from an unconnected computer in Tasks.
hî ---- Host: Is not ok, an unpredictable string is send.
Quote from: fred on September 27, 2010, 09:35:36 AM
1) When the computer goes off line, there may be some longer delays. The computer has to timeout first. After a couple of times the computer is regarded disconnected and things should go back to normal.
2) The update counter is linked to the last time it refreshed (wall clock) and the number of tasks, the more the slower it gets.
You may see the update of the history refresh. The history refresh is depended on the remaining time and has a maximum of 30 or 1/2 the expected remaining time.
1) Is the lightning symbol appearing at the same time host is timed out? So that when I see the lightning symbol, the computer should be in disconnected state and not part of the updating? Because the symbol was already there when the switching was delayed. It could have been that the reconnect time had passed when I tried. Or will tab switching always trigger a retry attempt?
Maybe regular updating and tab switching should be separated from the reconnection attempts? They should probably happen according to schedule and on background thread, IMHO. Additionally, an implicit menu command could be run by the user to trigger backgroun retry attempt (no "hidden" triggering for seemingly unrelated actions).
2) BT seems to go on overdrive sometimes (like it is at the moment) and is updating something every second. It claims to only have 36 tasks to update and I'm still only selecting only one computer (out of three that are all online). BT transfers about ~145kB total per second from all three hosts. That seems a bit excessive, although does seem to be affected according to number of tasks on the host. I guess this is history fetching that now gueries all tasks every second?
BT is on overdrive but the switching seems to be fast at the moment so I guess these are unrelated problems.
Quote from: wicked on September 27, 2010, 02:51:04 PM
1) Is the lightning symbol appearing at the same time host is timed out? So that when I see the lightning symbol, the computer should be in disconnected state and not part of the updating? Because the symbol was already there when the switching was delayed. It could have been that the reconnect time had passed when I tried. Or will tab switching always trigger a retry attempt?
Maybe regular updating and tab switching should be separated from the reconnection attempts? They should probably happen according to schedule and on background thread, IMHO. Additionally, an implicit menu command could be run by the user to trigger backgroun retry attempt (no "hidden" triggering for seemingly unrelated actions).
2) BT seems to go on overdrive sometimes (like it is at the moment) and is updating something every second. It claims to only have 36 tasks to update and I'm still only selecting only one computer (out of three that are all online). BT transfers about ~145kB total per second from all three hosts. That seems a bit excessive, although does seem to be affected according to number of tasks on the host. I guess this is history fetching that now gueries all tasks every second?
BT is on overdrive but the switching seems to be fast at the moment so I guess these are unrelated problems.
1) A background request is not a bad idea. At least something that doesn't slow down the displaying of data.
2) Only the selected computer is updated, but... the history is still running. The only way to get a reliable history is to request all results.
The history fetching depends on the time left from 1 - 30 seconds. = time left / 2 with a maximum of 30.
Quote from: fred on September 27, 2010, 01:40:08 PM
For the next version, I will not request temperatures from an unconnected computer in Tasks.
hî ---- Host: Is not ok, an unpredictable string is send.
May be - after restart, the text changed to e.g. "
13:12:49 ÈŠÆ ---- Host:", like:
27 september 2010 - 14:31:19 ÈŠÆ ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
27 september 2010 - 14:31:36 Host: localhost, Rpc Thread ID: 12120, dnetc_cpu_normal_1028373_1 ---- Update State
27 september 2010 - 14:31:44 ÈŠÆ ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname
27 september 2010 - 14:31:54 Connected ---- Host: localhost,Pavilon6,Port: 31417, TThrottle Version: 2.20
27 september 2010 - 14:31:57 Vetroplach, Connect ---- Invalid Socket
Quote from: Pepo on September 27, 2010, 01:17:50 PM
Quote from: fred on September 27, 2010, 12:39:18 PM
But do you have the reconnect ever xx second set.
Yes, at 710 sec.
Now the delay is around 1.5 sec.
Forgot to tell, setting the "Reconnect every..." to 0 seemed to have not much influence (at least on tab switching delay). Maybe just the "
17:23:11 ÈŠÆ ---- Host: vetroplach,Vetroplach,Port: 31416, Couldn't resolve hostname"-like strings were appearing less frequently than each 20-40 seconds (more precisely not at all during one 4-minute interval, but I did not recognize why).
Quote from: wicked on September 27, 2010, 02:51:04 PM
1) Is the lightning symbol appearing at the same time host is timed out? So that when I see the lightning symbol, the computer should be in disconnected state and not part of the updating? Because the symbol was already there when the switching was delayed.
Currently the red flash symbol is constatntly displayed for my remote computer. I've not noticed it - I do not use the
Sidebar computer selection - not that many machines at hand.
BT still runs as the same process since launched after upgrading to 0.75, the same single computer on a separate network. The switching time is now around 5 seconds, regardless of "Connect to TThrottle" and "Reconnect every..." settings.
I think that it has also little in common with responses from local BOINC client, as the BOINC Manager manages to get responses from the client on its regular 1-second intervals without any problem.
Quote from: Pepo on September 29, 2010, 06:54:54 AM
BT still runs as the same process since launched after upgrading to 0.75, the same single computer on a separate network. The switching time is now around 5 seconds, regardless of "Connect to TThrottle" and "Reconnect every..." settings.
I think that it has also little in common with responses from local BOINC client, as the BOINC Manager manages to get responses from the client on its regular 1-second intervals without any problem.
BOINC version?
Quote from: fred on September 29, 2010, 07:38:19 AM
Quote from: Pepo on September 29, 2010, 06:54:54 AM
BT still runs as the same process since launched after upgrading to 0.75, the same single computer on a separate network. The switching time is now around 5 seconds, regardless of "Connect to TThrottle" and "Reconnect every..." settings.
I think that it has also little in common with responses from local BOINC client, as the BOINC Manager manages to get responses from the client on its regular 1-second intervals without any problem.
BOINC version?
Still 6.11.6
Quote from: Pepo on September 29, 2010, 10:30:14 AM
:-[ :'(
I'm planning to switch over one of these days. ::)
Still on 0.75, will try to upgrade to 0.76 afterwards.
Quote from: Pepo on September 29, 2010, 06:54:54 AM
BT still runs as the same process since launched after upgrading to 0.75, the same single computer on a separate network. The switching time is now around 5 seconds, regardless of "Connect to TThrottle" and "Reconnect every..." settings.
I've again catched some black constellation of stars, tab switching takes the 20 seconds. A good moment for some network monitoring tests ;D
Quote from: Pepo on September 29, 2010, 06:54:54 AM
I think that it has also little in common with responses from local BOINC client, as the BOINC Manager manages to get responses from the client on its regular 1-second intervals without any problem.
I've looked at the list of BT's open connections and number of packets/bytes flowing in+out. Then switched to
History view - in this mode BT is pretty "silent" and transfers data really just occasionally.
After things settled down, I've started checking the network transfers and tried to hit either
Messages or
Transfers or
Tasks. In each case, the pattern was exactly the same:
AFTER the "Switched, busy..." message was gone, BT started to send/receive packets... ???
Thus I'm completely discarding any theory about network communication delays - it must be something BT-internal I believe.
Let's try Process Monitor...
While displaying the
Transfers view, BT was sending out 72-byte packets, approx. each second. While in the
History view, BT was regularly sending out 108-byte packets, approx. each 30 seconds, and 72-byte packets, approx. each minute.
There were also regular 67-byte packets in a-bit-more-than-minute intervals. Not tried to find out what it was.
Some 15 seconds prior to next
History update, when all three packet types appeared in last few seconds, I've touched the
Transfers tab. BT showed the "Switched, busy..." message for the remaining 15-20 seconds, when it was gone, then started to regularly communicate with 72-byte packets.
When switching from
Transfers (with 72-byte packets in 1-second interval) to
Projects, after a 23 second delay, 72-byte packets in 5-6-second interval appeared (the normal tasks update time).
Again, it must be something inside BT. I believe it is neither history fetching nor window refresh, something prior to it?
I'm gonna try 0.76.
Quote from: Pepo on September 30, 2010, 09:36:04 AM
Still on 0.75, will try to upgrade to 0.76 afterwards.
[...]
Again, it must be something inside BT. I believe it is neither history fetching nor window refresh, something prior to it?
I'm gonna try 0.76.
I'm just observing a 6 second "Switched, busy..." delay on BT 0.76 (BOINC 6.11.9 on Win7 x64). The BT process is running a week long.
Quote from: Pepo on October 07, 2010, 10:23:50 AM
I'm just observing a 6 second "Switched, busy..." delay on BT 0.76 (BOINC 6.11.9 on Win7 x64). The BT process is running a week long.
At 8 seconds delay just now. Whatever it could be...
Thinking a bit... if it would depend on the client, should a client restart (or just stop) change anything?
Quote from: Pepo on October 07, 2010, 12:52:21 PM
Quote from: Pepo on October 07, 2010, 10:23:50 AM
I'm just observing a 6 second "Switched, busy..." delay on BT 0.76 (BOINC 6.11.9 on Win7 x64). The BT process is running a week long.
At 8 seconds delay just now. Whatever it could be...
Thinking a bit... if it would depend on the client, should a client restart (or just stop) change anything?
As always trying is knowing.
But I suspect Windows more. A restart of BT will probably solve this. Maybe something is messed up, putting the system in sleep mode may get you into problems.
Quote from: fred on October 07, 2010, 12:59:07 PM
Quote from: Pepo on October 07, 2010, 12:52:21 PM
Quote from: Pepo on October 07, 2010, 10:23:50 AM
I'm just observing a 6 second "Switched, busy..." delay on BT 0.76 (BOINC 6.11.9 on Win7 x64). The BT process is running a week long.
At 8 seconds delay just now. Whatever it could be...
Thinking a bit... if it would depend on the client, should a client restart (or just stop) change anything?
As always trying is knowing.
But I suspect Windows more. A restart of BT will probably solve this. Maybe something is messed up, putting the system in sleep mode may get you into problems.
That is true. Unfortunately I've 2 Blender tasks, which have not checkpointed for hours (actually never). I've to wait a couple more hours...
And solving the problems by restarting BT might also lead to a very different conclusion ;)
This system was not hibernated for weeks already. We can strike at least this one.
Quote from: Pepo on October 07, 2010, 12:52:21 PM
Quote from: Pepo on October 07, 2010, 10:23:50 AM
I'm just observing a 6 second "Switched, busy..." delay on BT 0.76 (BOINC 6.11.9 on Win7 x64). The BT process is running a week long.
At 8 seconds delay just now. Whatever it could be...
The delay is now at around 35-60 seconds, on various tab pages and moments :P
Quote from: Pepo on October 07, 2010, 01:18:28 PM
Quote from: fred on October 07, 2010, 12:59:07 PM
Quote from: Pepo on October 07, 2010, 12:52:21 PM
Thinking a bit... if it would depend on the client, should a client restart (or just stop) change anything?
As always trying is knowing.
That is true. Unfortunately I've 2 Blender tasks, which have not checkpointed for hours (actually never). I've to wait a couple more hours...
Damn! Another DNETC cuda task with 5+ hours since the last checkpoint (and 2- days to go). Will probably not survive. [...] Have not survived a snooze. Let's restart the client... With a stopped client, the switching times are now 6 seconds. After starting a client, the switching times are 0 (zero) seconds.