Hope this post helps visualize which WS/CS process their WUs, and which don't/didn't, and since when.
For that, I added api-wu-crawling to my log analyzer and added a new type of output table:
Code: Select all
WS/CS-IP | #acct'd #newest-accounted-PRCG DATE TIME | #pending #oldest-pending-PRCG DATE TIME
128.174.73.74 | 45 Project:14916,Run:0,Clone:620,Gen:92 02/09 06:23 | - - - -
128.252.203.10 | 6 Project:14521,Run:0,Clone:396,Gen:256 02/07 20:50 | - - - -
128.252.203.11 | 1 Project:17219,Run:493,Clone:1,Gen:0 02/06 04:46 | - - - -
128.252.203.9 | 94 Project:17428,Run:0,Clone:2516,Gen:229 02/09 22:53 | - - - -
129.32.209.201 | 34 Project:16927,Run:22,Clone:1482,Gen:12 01/31 08:38 | 130 Project:16927,Run:17,Clone:591,Gen:45 01/18 15:07
129.32.209.203 | 117 Project:16933,Run:22,Clone:98,Gen:287 02/09 23:40 | - - - -
140.163.4.200 | 28 Project:17328,Run:3,Clone:229,Gen:14 02/09 23:41 | - - - -
140.163.4.210 | 32 Project:17800,Run:68,Clone:42,Gen:44 02/09 21:46 | - - - -
155.247.166.219 | - - - - | 14 Project:14188,Run:7,Clone:1469,Gen:1 01/19 09:39
18.188.125.154 | 30 Project:13445,Run:6576,Clone:36,Gen:1 02/09 16:03 | - - - -
206.223.170.146 | 44 Project:17425,Run:0,Clone:1266,Gen:132 02/09 22:40 | - - - -
66.170.111.50 | 77 Project:17415,Run:0,Clone:475,Gen:524 02/09 20:25 |
For above table, my script analyzed all log lines between January 18th and February 9th (UTC) from 8 of my folding systems for successfully submitted WUs, and the PRCG for each WU was queried from
https://apps.foldingathome.org/wu to check if my username was listed for that PRCG.
If it was, that WU is counted as "accounted for", and the number of accounted-for WUs per WS/CS is in column2 ("#acct'd"), and for reference, the PRCG and date/time of the newest WU accounted-for by that WS/CS is also shown.
If it wasn't, that WU is counted as "pending", and the number of pending WUs per WS/CS is in column6 ("#pending"), and for reference, the PRCG and date/time of the oldest "pending" WU by that WS/CS is also shown.
It can be seen that two CS/WS are still backlogged, even after the latest "drop" 8 hours ago:
129.32.209.201 (vav18.fah.temple.edu | voelz)
155.247.166.219 (vav3.ocis.temple.edu | voelz)
155.247.166.219 just didn't stat-account any WU for me (and presumably anybody else) since at least January 19, which is the "normal" scenario for backlogged stats and will most likely rectify itself once that machine's backlog is taken care of.
129.32.209.201 tells a different, more interesting story: It did account for a seemingly-random subset if "my" WUs between at least January 18th and January 31st, to then stop accounted any of "my" WUs since January 31st, 08:38am. Is there a good hypothesis of what can cause a behavior were just a seemingly-random (in time) subset of WUs is stats-processed? (all submitted to the same CS/WS IP!)
