fprintf isn't inactive/not working, as much backgroundPool doesn't capture the "diary" of parfeval. This has the same behaviour as threaded pools
f = parfeval(parpool('threads'),@foo,1,10);
And it has a similar behaviour as process pools
f = parfeval(parpool('local'),@foo,1,10);
with one exception. With a process pool, in the while-loop you could add the call
f.Diary
It won't do exactly what you want -- it'll print the entire diary each time. For example
ans =
1
2
3
4
5
6
7
8
9
ans =
1
2
3
4
5
6
7
8
9
10
But to your point, if instead of calling
f = parfeval(backgroundPool,@foo,1,10);
you called
parfor i = 1:1
res = foo(10);
end
you would see the fprintf statements. I'll check with Development, but it would appear as thought screen I/O would be the gating functions.
