Re: [bug-gawk] Performance observations while using getline: reading from a pipe vs. using a coprocess

[Hermann Peifer]

On 2013-04-08 14:44, Aharon Robbins wrote:
> Hi Hermann.
>
> As noted by others, in the pipe case, you are closing and reopening
> the pipe for *every* input record.  This means creating a new
> process for every input record, whereas for the co-process case, you
> are doing the close at the end, so you only create one process and you
> continuosly feed it data.

Thanks for the exlanation. I do understand that the observed performance 
issue is unrelated to gawk

> I suspect that if you change the pipe case to do the close at the
> end you will see more reasonable performance.

In the given case, this is not an option. Each pipe has an individual 
name which includes values from the data file. If I don't close the pipe 
immediately, then sooner or later, I will end up with:

fatal: cannot open pipe `Geod -i --input-string '51.1166 99.7882 
-36.1137 -164.263'' (Too many open files)

Thanks again for the time, Hermann