Le 14/10/2014 14:15, David T. Lewis a écrit :
On Tue, Oct 14, 2014 at 07:19:10AM +0200, Thierry Goubier wrote:
Hi Dave,
took me a while to do some testing. It seems there is an issue, but I
couldn't find out where. First, the data:
Loading a package from a local gitfiletree repository (get from the
command a zipped git archive containing the package) :
4.5.11, 4.6.8: 2132 msec.
4.5.12, 4.6.9: 50847 msec.
I tried to rewrite the main command, remove the closePipes, etc... No
change in the runtime, so your right.
Profiling doesn't help much: execution time is mostly idle time (but
with a significant increase on PipeableOSProcess commands: goes from
invisible to 2700 ms. A user break in the middle shows it delay waiting
on output of the external process).
Only hint I could see is that it seems to be linked with the size of the
output of the command.
Thierry,
Aha! I am quite sure that you have located the problem. There must be
something preventing the OS process from running to completion with
a larger amount of output data. It definitely sounds like a bug in my
latest update to Pipeable OSProcess.
The strange thing is that it runs to completion (i.e. I got no errors;
if any data was missing or corrupted on output, my load would fail); but
a lot slower than it should be.
Thank you very much for finding this. I will get it fixed as quickly
as I can.
Thanks. I'm unable to help you much, I'm afraid :(
Thierry
