[RFC] New feature: --batch to accept command sequences from stdin (or file)

[Michael Ellerman]

On 6/22/06, Jari Aalto+mail.linux <jari.aalto at cante.net> wrote:
> * Wed 2006-06-21 Diwaker Gupta <diwaker.lists AT gmail.com>
> * Message-Id: 891be9410606211613u5cb057b1gd92c4417123d0cb6 AT mail.gmail.com
> >> Originally I was more thinking the language interpreter startup time,
> >> which I expected to be the problem. In PII 400Mhz/512M/W2k/Cygwin this
> >> command
> >>
> >>    $ time python -c "exit;"
> >>
> >> takes average of 1.5 sec (real). To run 3 commands in series, it would
> >> take total:
> >
> > Yikes! On all of my boxes, this takes roughly 100 times less. What
> > _is_ the configuration of your machine?
>
> This is pretty "modern" machine considering its age:
>
> - PII 400Mhz, 512M ECC, 33Mhz bus
> - Promise SATA300 TX2plus (2 x PCI 133, 2 x SATA 300) controller
>   1) 1 x SATA 400G / WD4000KD SE16 (brand new), UDMA 6, 7200 rpm, 16MB
>   2) 2 x IDE  160G / Samsung Spinpoint SP1604N 7200 rpm, 8MB buffer
> - W2K, SP4 + all the serious/critical security fixes

Dude, that's not a modern machine. I bought a pIII 700 Mhz system _8_
years ago. You might have decent disk, but the rest of it is ancient.
Which is fine, I'm not dis'ing you, but just to set expectations ..
that's never gonna be real fast. :)

> In W2k/Cygwin this is linear[1], because the operating system does not
> sem to cache, like it does in Linux.

> root at w2kpicasso:/cygdrive/e/home/jaalto# for i in 1 2 3 4 5 6 7 8 9 10;
> do time python -c "exit;"; done
>
> real    0m1.533s
> user    0m0.280s
> sys     0m1.142s
>
> real    0m1.535s
> user    0m0.300s
> sys     0m1.161s

Wow, that's super lame. I wonder if it's Cygwin, or if windows really
does just suck ;)

cheers