Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 5/3/83; site ukc.UUCP
Path: utzoo!watmath!clyde!burl!hou3c!hocda!houxm!hogpc!houti!ariel!vax135!ukc!lfm
From: lfm@ukc.UUCP
Newsgroups: net.unix-wizards
Subject: scheduling/timing weirdo
Message-ID: <4170@ukc.UUCP>
Date: Fri, 4-May-84 14:25:56 EST
Article-I.D.: ukc.4170
Posted: Fri May  4 14:25:56 1984
Date-Received: Sat, 28-Apr-84 09:21:55 EST
Organization: Computing Lab. Kent University, England
Lines: 26

Can anybody enlighten me as to why the following things happen :

1) When testing some code that interacts with a server on a remote machine
I replaced a programmed C copy loop with a call on a fast move subroutine,
as expected the user time as reported by "time(1)" dropped significantly.
However, the system time increased considerably, and the elapsed stayed
about the same. This was repeatable and consistent, and the program was
unmodified in any other way. (PDP11/45 and V7 by the way).

2) (This time on a PERQ running PNX - a V7 port) This time the
optimisation was put into the file server end, so the program running
locally was completely unchanged. When the test was run again the system
time increased significantly and consistently. The time was measured
was only local and could not include any of the time on the remote machine.
No extra messages were generated by the communication between the processes
(A first thought was that with the speed increase things were running too
fast and retries were happening) and the local process cannot have done
anymore work than it would have before the change to the server.

So, any suggestions?

  Lindsay F. Marshall
    uucp : ...!{mcvax,vax135}!ukc!lfm
    ARPA : Lindsay_Marshall%NEWCASTLE@MIT-MULTICS
    post : Computing Laboratory, U of Newcastle upon Tyne, U.K.
           +44 - 632 - 329233 xtn 212