On Fri, Jun 19, 2015 at 1:42 PM, Ian Boston <[email protected]> wrote: > ...Its existing code that is triggered by a Job and calls flush every line > output to ensure a UI is updated. The flush has been removed, but users > will probably complain that nothing appears to be happening without the > flush...
Ok, a middle ground might be to flush but not more often than every N minutes, to have a predictable latency. > > I have suggested that the existing code avoid the BGServlet already using a > service called from a Job, but I am almost certain other things use it... Yeah, deprecating this will take some time, as usual. > > ...We observed 28K nodes created per invocation to store 300K of output, which > obviously consumed nearly all of the repository (MongoMK) write capacity, > as each flush also saves... Ouch...so as I said I don't know if this can work without creating multiple nodes on Oak, but open to making changes if you have suggestions. I have little time until the end of next week though. -Bertrand
