Why does Task not show recent history -- just In Progress / Pending?
Message boards :
Number crunching :
Why does Task not show recent history -- just In Progress / Pending?
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 29 Sep 09 Posts: 18 Credit: 46,059 RAC: 0  
|
Why does Task not show recent history -- just In Progress / Pending? I would be nice to see what credit was being received. |
 arkayn Send message Joined: 14 Feb 09 Posts: 999 Credit: 74,932,619 RAC: 0  
|
I'm lowering the purge time (sorry) to help speed up the database. This should hopefully improve response time for the webpage and downloading new workunits. http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1510#36306 
|
banditwolf Send message Joined: 12 Nov 07 Posts: 2425 Credit: 524,164 RAC: 0  
|
Why does Task not show recent history -- just In Progress / Pending? I would be nice to see what credit was being received. With the volume of tasks processed each day it bogs the server down too much. It has been under 12 hours for most of the project. It's the easy way to take stress off the server instead of building a better one. Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. |
|
Paul D. Buck Send message Joined: 12 Apr 08 Posts: 621 Credit: 161,934,067 RAC: 0 
|
Why does Task not show recent history -- just In Progress / Pending? I would be nice to see what credit was being received. The current payment seems to be 213 and change per task. MW is the victim of its own success and open source ... :) With heavy hitters looking at the code we have one of the best suites of applications across the span of resources, both CPUs and the two types of GPUs at this project... so, though they have increased the work effort per task these tasks are very well suited for GPU processing ... and so, I am looking at one system and it is taking ~3:23 per task ... two GPUs and that means I am completing a new task in just over a minute and a half on average ... or, thousands of tasks per day on just that one system ... When you multiply that times the number of people here you get very long lists of tasks and that increases the work that the database must perform... so, to keep the work level down the project purges completed tasks very quickly from the database. Frustrating if you want to look up specific tasks or look at them a day or so later ... but ... project wise, completed tasks in the database of of no value whatsoever ... thus the "insta-purge" where the tasks have short lives in the database... It is not that the project would not like to build a better system, it is the cost of doing so ... |
©2024 Astroinformatics Group