The next thing I'm wondering now: should we include an optional bound to the global workqueue size in the API ?
I've just had cases here where I stress test the queue with very frequent dispatch, and it can fill up memory relatively quickly if the workers have a large amount of work to do per work-item. I think the usual way to do this would be to make the behavior nonblocking when the queue is full, so the dispatcher can take action and move the work away to another machine, or report congestion. Thoughts ? Thanks, Mathieu -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
