stephen@comp.lancs.ac.uk (Stephen J. Muir) (01/13/87)
We're running BSD 4.2 and our system has recently been giving a very poor response, sometimes, when the load average is below 1.0. There is nothing being printed on the console, so I'm rather at a loss. Can anyone give me any pointers please? -- EMAIL: stephen@comp.lancs.ac.uk | Post: University of Lancaster, UUCP: ...!mcvax!ukc!dcl-cs!stephen | Department of Computing, Phone: +44 524 65201 Ext. 4120 | Bailrigg, Lancaster, UK. Project:Alvey ECLIPSE Distribution | LA1 4YR
lkc@hpirs.HP (Lee Casuto) (01/21/87)
One possible reason is that your file system(s) are nearly full with the most recently accessed files being the furthest away form the heads. If this is the problem, the solution is to back up the file systems sorted on access (modification) time. Do a mkfs the file system. Restore the files on the new file system. This has been reported to increase performance dramatically. Lee Casuto ...ucbvax!hpda!lkc
mmm@iconsys.UUCP (02/05/87)
Oftentimes, I have seen serial ports that were not terminated
properly (i.e. when the terminal is turned off) have problems
with line ringing. What happens is that a character is generated
on the line, echoed by the host, then reflected back to the
host again, ad infinitum. This can really affect performance,
especially if you have more than one line going.
Doing an iostat or equivalent will display the amount of character
traffic, and if this is high when there is no good reason for it,
line ringing could be your problem.
One solution is to always log out before turning off a terminal
(a good idea anyway), because getty will not echo forever. Another
solution might be to check your hardware and make sure your lines are
terminated properly.
--
Mark Muhlestein @ Icon International Inc.
{ihnp4,decvax,seismo!ut-sally}utah-cs!utah-gr!uplherc!nrc-ut!iconsys!mmm