store progress not in jobDB but in a map[job_id]progress

Store progress not in jobDB but in a map[job_id]progress. This prevents 
excessive persisting of the jobDB, allows updating independent of the 
jobDB-handling goroutine and allows faster updating. This may improve 
performance of mass installations with their many progress messages.

The drawback of course is that the progress can no longer be observed by 
external programs by looking at jobdb. But how important is that?

To decide if this feature is worth it, simulate the FAI messages (only the FAI 
messages) from 1000 concurrent softupdates and test responsiveness of GOsa 
during that. Also look at go-susi --stats output at message response time.
Then do the same test after disabling CLMSG_PROGRESS completely. Is the 
difference worth it?

Original issue reported on code.google.com by mux2...@gmail.com on 11 Jul 2013 at 6:43

google-code-export / go-susi

store progress not in jobDB but in a map[job_id]progress #135