Thanks for the info Mark.I'm sure Eric and Matt will make sure that they purchase equipment that is more than adequate for the job. Thanks to HP for the 20% discount.A bright future is in store for SETI hopefully in a few weeks time. And thanks to you Mark for having the foresight to run the two funding drives before the total crash. Without your help it would be a very bleak picture for SETI.
Just heard from Eric again.........They are still trying to get jocelyn up to speed to handle mork's duties.......not sure when or how well she might perform once configured.
Quote from: msattler on 19 Oct 2010, 06:27:42 pmJust heard from Eric again.........They are still trying to get jocelyn up to speed to handle mork's duties.......not sure when or how well she might perform once configured.They'll need to keep the query rate down - both the number of queries, and the size of the result recordsets.Quota is a bad tool for that. If it's high, the database, and the recordsets, get huge. If it's low, the client work request rate gets huge - probably two or three work requests per completed task (not done an exact count). With a multi-CUDA host finishing a task every couple of minutes, that'll reduce Jocelyn to a heap of smoking ashes the first day.My judgement would be to keep quota (to keep the size down), but to add a scheduler server-requested backoff of something realistic - say 10 minutes. That wouldn't be any hardship to multi-CUDA - report five, get five, instead of report one, get one - but it would slow down the request rate dramatically.
Quote from: Richard Haselgrove on 19 Oct 2010, 06:52:36 pmThey'll need to keep the query rate down - both the number of queries, and the size of the result recordsets.Quota is a bad tool for that. If it's high, the database, and the recordsets, get huge. If it's low, the client work request rate gets huge - probably two or three work requests per completed task (not done an exact count). With a multi-CUDA host finishing a task every couple of minutes, that'll reduce Jocelyn to a heap of smoking ashes the first day.My judgement would be to keep quota (to keep the size down), but to add a scheduler server-requested backoff of something realistic - say 10 minutes. That wouldn't be any hardship to multi-CUDA - report five, get five, instead of report one, get one - but it would slow down the request rate dramatically.Whatever it takes to keep things alive until the cavalry arrives........You won't hear any complaining from me.Have you passed your suggestions on to Eric?
They'll need to keep the query rate down - both the number of queries, and the size of the result recordsets.Quota is a bad tool for that. If it's high, the database, and the recordsets, get huge. If it's low, the client work request rate gets huge - probably two or three work requests per completed task (not done an exact count). With a multi-CUDA host finishing a task every couple of minutes, that'll reduce Jocelyn to a heap of smoking ashes the first day.My judgement would be to keep quota (to keep the size down), but to add a scheduler server-requested backoff of something realistic - say 10 minutes. That wouldn't be any hardship to multi-CUDA - report five, get five, instead of report one, get one - but it would slow down the request rate dramatically.
unfortunately, they went offline at some point during the night or very early morning. Back to square one?
21 Oct 2010 1:50:22 UTC Our capacity is a bit dicey right now. So to keep things from getting out of hand while we are not watching, we are running uploads only over night and will turn on downloads tomorrow morning (pacific time).
