home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.aix
- Path: sparky!uunet!cs.utexas.edu!milano!cactus.org!chukran
- From: chukran@cactus.org (Rudy E. Chukran)
- Subject: Re: RS6000 almost stops with heavy disk access.
- Message-ID: <1992Nov19.070106.8255@cactus.org>
- Organization: Capital Area Central Texas UNIX Society, Austin, Tx
- References: <199211171808.AA15477@cc.ysu.edu>
- Date: Thu, 19 Nov 1992 07:01:06 GMT
- Lines: 24
-
- In article <199211171808.AA15477@cc.ysu.edu> JOAOLSD@vm1.sdi.uam.es (Joao Luis Silva Damas) writes:
- >Hi,
- >we have two rs6000 (a 320H and 340) being used by different kinds of users.
- >Some of them do large molecular calculations which create HUGE (600-700 MB) tem
- >porary files for the molecular integrals. When their program begins writing the
- >se huge files and then reading them as needed, our machines almost stop and oth
- >er users are almost unable to use the system. The slowness means 30-60 sec to l
- >ogon, 1 minute for X windows to create a new window, a long time for even an ls
- >, etc. Most other users do a lot of editing so they actually need better respon
- >se time from the machine.
- >Is there anyway to correct this situation (besides killing those huge calculati
- >ons, of course)?
-
- Lower the priority of the cruncher programs with nice or renice.
-
- Look into using the I/O write queue length limitation feature. Ther is
- a panel in SMIT to do this. However, describing how to do it here is quite
- difficult. Id suggest playing with some nonzero values and see if that helps.
- Cant give you more info since Im not in front of my 6000 right now.
-
- Add more memory.
-
- Add faster disks or more disk arms and rearrange the files on those drives.
-
-