Re: [EXTERNAL] Re: Performance issues using GAWK 3.1.6 ->from Win 2008 to Win 2016

[Andrew J. Schorr]

On Tue, Jun 15, 2021 at 04:10:41PM +0300, Eli Zaretskii wrote:
> > From: "Koleti, Haritha" <Haritha.Koleti@pseg.com>
> > CC: "wolfgang.laun@gmail.com" <wolfgang.laun@gmail.com>,
> >         "bug-gawk@gnu.org"
> >     <bug-gawk@gnu.org>,
> >         "Pereira, Ricardo" <Ricardo_D.Pereira@pseg.com>,
> >         "Pirane,
> >  Marco" <Marco.Pirane@pseg.com>
> > Date: Tue, 15 Jun 2021 12:53:59 +0000
> > 
> > Thanks Ed. 
> > 
> > But why same script worked in 10 mins in the Windows 2008 and now it is 
> > taking 90 mins in 2016 ?
> 
> How large is Emp_attr.csv?  If it is very large, perhaps the newer
> system gives you less memory, and starts paging as result?
> 
> Or maybe some of the functions in the system libraries used by Gawk
> became much slower in Server 2016 (a.k.a. Windows 10)?
> 
> In any case, if the run time is reduced to seconds, the difference
> shouldn't matter anymore, even if it persists.

And also: is the D drive in the new system somehow slower than
the old drive?

And how fast is the DOS TYPE command and pipe implementation? The
existing code says:

TYPE  ParentChild.csv|gawk -f Emp_Attr.awk>Emp_Attr.csv
TYPE  ParentChild.csv|gawk -v f2=Emp_Attr.csv -f map_attr.awk>Map_Attr.csv

Why not simply say instead:

gawk -f Emp_Attr.awk ParentChild.csv>Emp_Attr.csv
gawk -v f2=Emp_Attr.csv -f map_attr.awk ParentChild.csv>Map_Attr.csv

That would be in addition to Ed's rewrite of map_attr.awk,
assuming that there's enough memory on the system to
contain the data in Emp_Attr.csv.

Regards,
Andy