Back to the main page.
Bug 278 - implement MaxBusy option in peercellfun
| Status | CLOSED FIXED |
| Reported | 2010-12-08 12:16:00 +0100 |
| Modified | 2011-01-05 12:01:05 +0100 |
| Product: | FieldTrip |
| Component: | peer |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P1 normal |
| Assigned to: | Robert Oostenveld |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Robert Oostenveld - 2010-12-08 12:16:03 +0100
This option should limit the number of slaves that are simultaneously working. The decision for this is in the hands of the end-user. e.g. peercellfun(@pause, {1, 1, 1, 1, 1, 1, 1, 1, 1, 1}, 'maxbusy', 1) should take 10 seconds and peercellfun(@pause, {1, 1, 1, 1, 1, 1, 1, 1, 1, 1}, 'maxbusy', 2) should take 5.
Robert Oostenveld - 2010-12-08 22:36:07 +0100
in revision 2359 I added a MaxBusy option to peercellfun to limit the number of slaves that is kept busy on a single collection of jobs
Robert Oostenveld - 2011-01-05 11:57:00 +0100
selected a long list of resolved bugs from roboos and changed the status into "RESOLVED"