[Swift-devel] coaster status summary

[Mihael Hategan]

On Mon, 2008-04-07 at 12:49 +0000, Ben Clifford wrote:
> Wary of excessive optimisation of job completion notification speed in 
> order to get high 'trivial/useless job' numbers, when there also seem to 
> be problems getting shared filesystem access fast enough for non-useless 
> jobs. Getting a ridiculously high trivial job throughput is not (in my 
> eyes) a design goal of this coaster work.

200 j/s should be enough for anybody.

Joking aside, the issue was ability to scale to large number of jobs
rather than speed. But it looks like the issue is only an issue for
monsters such as the BG/P.

>