The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Diomidis Spinellis <dds@aueb.gr>
To: Marc Rochkind <mrochkind@gmail.com>, Bakul Shah <bakul@iitbombay.org>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Perkin-Elmer Sort/Merge II vs Unix sort(1)
Date: Sat, 18 Jan 2025 16:51:15 +0200	[thread overview]
Message-ID: <c210583f-4417-4b1e-a0ed-4c9ab1fcaac0@aueb.gr> (raw)
In-Reply-To: <CAOkr1zXMAoBJL0qXAD42Qz5WECkbgW7UWUpF=wy9cGCWt38qEQ@mail.gmail.com>

I gave specific examples of facilities offered by the Perkin-Elmer 
Sort/Merge, (file allocation, blocking, interactive and batch modes) 
that on Unix systems are handled in a way that allows all programs to 
benefit from them.  The Unix way reduces duplication and makes the 
system more versatile by offering the facilities to all programs.

I based my comparison on the documented facilities of the two programs. 
I also have some first hand experience with Perkin-Elmer's OS/32.  In 
the 1990s I was involved in servicing and transferring some 
record-keeping applications from a Perkin-Elmer running OS/32 and 
RELIANCE to a Unix system running Ingres.  I found I was a lot more 
productive in Unix's shell than in Perkin-Elmer's MTM.  (Admittedly, 
this could also be a matter of experience.)

In 2018 I used the Unix sort and join commands to speed up a MariaDB 
relational join of a five billion row table with a 847 million row table 
(108 GB in total) from 380 hours to 12 hours [1], so I'm very happy with 
how Unix sort can handle moderately large data sets.  The GNU version 
will even recursively merge intermediate files when it runs out of file 
descriptors.  Even the Seventh Edition sort would overflow to temporary 
files and merge them [2].

I'm sure the mainframe sort programs did some pretty amazing things and 
could run circles around the puny 830 line Unix Seventh Edition sort 
program.  The 215 page IBM DOS VS sort documentation that John Levine 
posted here is particularly impressive.  But I can't stop thinking that, 
in common with the mainframes these programs were running on, they 
represent a mindset that has been surpassed by superior ideas.

[1] https://www.spinellis.gr/blog/20180805/
[2] 
https://github.com/dspinellis/unix-history-repo/blob/Research-V7/usr/src/cmd/sort.c#L350

Diomidis

On 17-Jan-25 21:35, Marc Rochkind wrote:
> Why did you say "thoughtless agglomeration of features?"
> 
> Do you know anything about the design of the P-E S/M, or is just a 
> biased guess? Have you ever tried a large external sort with UNIX commands?
> 
> Marc

  reply	other threads:[~2025-01-18 14:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 17:23 [TUHS] " Diomidis Spinellis
2025-01-17 19:10 ` [TUHS] " Bakul Shah via TUHS
2025-01-17 19:35   ` Marc Rochkind
2025-01-18 14:51     ` Diomidis Spinellis [this message]
2025-01-18 15:16       ` Larry McVoy
2025-01-18 15:40         ` Paul Winalski
2025-01-18 16:54           ` Marc Rochkind
2025-01-19  3:45           ` sjenkin
2025-01-18 16:00         ` Bakul Shah via TUHS
2025-01-18 16:25           ` Tom Lyon
2025-01-18 17:07             ` ron minnich
2025-01-18 19:39               ` Marc Rochkind
2025-01-17 20:07 ` John Levine
2025-01-18  4:46   ` Dave Horsfall
2025-01-17 18:12 Douglas McIlroy
2025-01-18  4:29 ` G. Branden Robinson
2025-01-21 21:53 Douglas McIlroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c210583f-4417-4b1e-a0ed-4c9ab1fcaac0@aueb.gr \
    --to=dds@aueb.gr \
    --cc=bakul@iitbombay.org \
    --cc=mrochkind@gmail.com \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).