Sorry this took some time to summarise but I've been talking to our LISP
supplier again about this.
The original question was concerned with the lack of speed of our LISP package
under OSF/1 v3.0.
Thanks to those that replied:
Knut Helleboe
Richard Jackson
David Hegarty
alan_at_nabeth.cxo.dec.com
lispworks-support_at_harlequin.co.uk
On Alans suggestion I also got a copy of the monitor program from gatekeeper and
looked at the values it reported whilst the LISP was running. I sent off lots
of info to Harlequin - our lisp supplier, and got some ideas about what to do to
fix the problem.
The main problem is that the machine is paging itself to death. This was
confirmed by all the checks that I ran.
The recommended solution is to increase the amount of physical memory to 64 MB
and/or get another faster disk. This would mean that the system would not need
to page so much or when it was paging it at least paged to another disk.
Knut suggested that as 3.0 is bigger it may need 64MB anyway and to check that
we are running in lazy swap mode - no /sbin/swapdefault. We are and always have
been in lazy swap.
Richard reported that DEC had said that v3.2 fixed a memory leak in v3.0.
Harlequin after getting a mass of data replied saying that the problem is paging
and giving example vmstat results from their machines. These showed that with
64MB of memory there were no problems.
So it looks like I've got to persuade my boss to dig into his pockets and buy
more memory and possibly more disk.
Thanks for everyones help.
John.
********************************************************************************
John Richards * email : john_at_zyqad.co.uk
Zyqad Ltd, *
Suite 25, GPT Business Park, *
Technology Drive, Beeston * tel : 44 (0)115 922 0820
NOTTINGHAM. NG9 2ND. * fax : 44 (0)115 967 8374
********************************************************************************
Received on Tue Jul 18 1995 - 14:03:55 NZST