Re: run-shell-command timing

[fritzson@PRC.Unisys.COM]

> Date: Mon, 11 Sep 89 11:38:36 PDT
> From: smh@Franz.COM (Steve Haflich)
> 
> I have a partial analysis of this problem.  Before committing to a
> complete analysis, I'll need to know on what platform you are running,
> the version of its OS, and which version of Allegro.  Also, I'm
> betting that multiprocessing is running, i.e., the lisp scheduler has
> been started.  Right?
> 

I appreciate your working on this. Multiprocessing was in fact running
when I ran the test that I mailed out. But, with multiprocessing off I
still get the same effect.

The platform is a SUN 3/60 running SUN OS 3.4. Here's a session. The
very first command issued is (dribble-bug "foo").


dribbling to file "/bio/fritzson/foo"
 
LISP-IMPLEMENTATION-TYPE: Allegro CL
LISP-IMPLEMENTATION-VERSION: 3.1.beta.22 [Sun3] (6/7/89)
MACHINE-TYPE: Sun3
MACHINE-VERSION: 
SOFTWARE-TYPE: SunOS
SOFTWARE-VERSION: 
SHORT-SITE-NAME: portia
*features*: (:UNIX :SUN3 :M68K :SUN :IEEE :CONFORMING-IEEE :ALLEGRO :COMMON-LISP :EXCL :FRANZ-INC :GSGC :ALLEGRO-V3.1)
*modules*: ("ADVISE" "TRACE" "INSPECT" "SA68881")
PATCH::*PATCHES*:
 (75 . "Fix mapl function")

NIL 
<cl> :cl mail-lisp

; Fast loading /sun/bio/fritzson/mail-lisp.fasl.
<cl>  ;; read direct from stream
(time (length (read-user-info t)))
cpu time (non-gc) 8001 msec user, 15434 msec system
cpu time (gc)     1416 msec user, 150 msec system
cpu time (total)  9417 msec user, 15584 msec system
real time  33860 msec

269 
<cl>  ;; read from a file
(time (length (read-user-info ())))
cpu time (non-gc) 6383 msec user, 283 msec system
cpu time (gc)     800 msec user, 200 msec system
cpu time (total)  7183 msec user, 483 msec system
real time  11540 msec

269 
<cl> :proc
The scheduler is not running.
<cl> (dribble)