Johan Corveleyn wrote on Thu, Aug 30, 2012 at 09:11:08 +0200: > On Wed, Aug 29, 2012 at 4:22 AM, Justin Erenkrantz > <jus...@erenkrantz.com> wrote: > > On Tue, Aug 28, 2012 at 7:22 PM, Johan Corveleyn <jcor...@gmail.com> wrote: > >> Yep, redirecting to a file eliminates the bottleneck (almost the same > >> as redirecting to NUL) (I ran it a couple of times to make sure the > >> server cache was hot): > > > > FWIW, I've historically seen similar behavior on Unix platforms as > > well - especially on machines with SSDs and a fast local network as > > the stdout I/O to emit the notifications is the slowest part of the > > system by far. -- justin > > Hmz, so contrary to what I thought it seems it's not only a problem on > Windows. Is is as severe on *nix as on Windows? My export (w/ fast > server over a LAN) was twice as fast when redirecting notifications to > a file. Can somebody get some numbers on some unixy platform? > > But more to the point: anybody have a solution in mind? If it's not > Windows-only then some Windows defines wont help of course.
Does not follow. Windows defines won't fix the Unix problem but might fix the Windows problem. > Buffering > the output may be the only way to eliminate this bottleneck? What are > the pros and cons, and how hard would that be? Any other ideas? > > -- > Johan
