Thread: Re: [ADMIN] Speed problem

Re: [ADMIN] Speed problem

From
Roger Books
Date:
After conferring with Jan Weick I removed the index I had on the
database in question and that seems to have solved my problem.
A corrupt index is a bad thing.

On the memory issue, I'm running PII-300's with 128MB of RAM.
while memory is always full (this machine is also running bind)
and has stuff swapped, there is actually very little swapping
going on.  Maybe it's just me but I don't recall ever seeing
a Unix box that didn't have something swapped.  Normally those
are procs that are doing nothing.  Now, I'm no expert on this
particular program, however, from previous experience...

If you are getting incremental slow downs on a program and
your swap space is not growing at the same rate slow swap
would not be high on my list of suspects.

Roger Books

Re: [ADMIN] Speed problem

From
"Gene Selkov Jr."
Date:
> On the memory issue, I'm running PII-300's with 128MB of RAM.
> while memory is always full (this machine is also running bind)
> and has stuff swapped, there is actually very little swapping
> there is actually very little swapping going on.

Full memory does automatically mean swapping is going on. It may be
filled up with the filesystem cache, which is normally allowed to
grow as much as it can until other processes request for more memory.

> Maybe it's just me but I don't recall ever seeing
> a Unix box that didn't have something swapped.

Two other things to consider. One is that it is almost impossible
to see a Unix box not running Netscape (unless it is an unattended
sever). All linux versions of Netscape after 2.* had various memory
leaks. 4.*s do something wrong to the swapping, such that a lot of
swap space is not getting reclaimed even after you kill them. Netscape
in linux is also known to leave non-functional child processes in
memory. In short, if you are in linux, make sure Netscape hasn't
been run since the system is up, in order to examine memory problems.

Other thing is, you can't always trust information reported by ps.
The last time I had problems with a large COPY (also reported by a
number of others), my machine was swapping badly, memory was taken up
but ps, even though it listed postgres as the top process, reported
only 3Mb memory usage.

--Gene