If the transitioner is backlogged, the work generator is called to create more work. But, since the transition creates the results, the server things that there isn't any work so it creates more. That causes the transition to get even more bogged down trying to create the result records. Collatz is only supposed to have 1K of workunits per app. As a result of the "catch 22" described, there are almost 500,000 WUs now. That causes the database to grow even larger and when it exceeds the physical RAM, MySQL slows down considerably which makes the transitioner even slower causing even more workunits to be generated.
So... is there any way that the work generator can check not only that the count of WUs per appid is below the threshhold but also that the transitioner is not backlogged prior to generating more work? Jon Sonntag _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
