Ok, I was able to run a vacuumdb -f -v on my largest db over the weekend.
However, I am having trouble reading the results of the table portion. Here
area a couple of tables, what should I be looking at. First table is the key
table to the db, and the second is the largest table in the db.
Your second server has queuing (load averages are highish), only 2 processes
running, and almost all cycles are idle. You need to track down your
bottleneck. Have you looked at iostat/vmstat? I think it would be useful to
post these, ideally both before and after full vacuum analyze.
/Aaron
Chris,
I need some help. I have 5 db servers running our database servers, and
they all are having various degrees of performance problems. The problems
we are experiencing are:
I'mm confused. You're saying general slowness but say that most queries run
in under .01 seconds. And you say
On Fri, 23 Apr 2004, Chris Hoover wrote:
DB's on Powervaults 220S using raid 5 (over 6 disks)
What controller is this, the adaptec? We've found it to be slower than
the LSI megaraid based controller, but YMMV.
Running RH ES 2.1
Are you running the latest kernel for ES 2.1? Early 2.4
I know the numbers look ok, but we are definetly suffering. Also, if I try to
run any sort of vacuum or other db activity during normal business hours,
load goes through the roof. I have seen loads of over 10 when trying to
vacuum the larger cluster and would have to kill the vacuums due to
Sorry for the confusion here. I can't run any sort of vacuum durin the day
due to performance hits. However, I have run vacuums at night. Several
nights a week I run a vacuumdb -f -z on all of the clusters. I can take
serveral hours to complete, but it does complete.
During the day, I
Chris,
Sorry for the confusion here. I can't run any sort of vacuum durin the day
due to performance hits. However, I have run vacuums at night. Several
nights a week I run a vacuumdb -f -z on all of the clusters. I can take
serveral hours to complete, but it does complete.
Well, here's
Josh Berkus wrote:
Chris,
Sorry for the confusion here. I can't run any sort of vacuum durin the day
due to performance hits. However, I have run vacuums at night. Several
nights a week I run a vacuumdb -f -z on all of the clusters. I can take
serveral hours to complete, but it does
On Friday 23 April 2004 14:57, Ron St-Pierre wrote:
Does this apply to 7.3.4 also?
Actually, since he's running 7.4, there's an even better way. Do a
VACUUM VERBOSE (full-database vacuum --- doesn't matter whether you
ANALYZE or not). At the end of the very voluminous output, you'll see
On Fri, 23 Apr 2004, Chris Hoover wrote:
On Friday 23 April 2004 13:21, scott.marlowe wrote:
On Fri, 23 Apr 2004, Chris Hoover wrote:
DB's on Powervaults 220S using raid 5 (over 6 disks)
What controller is this, the adaptec? We've found it to be slower than
the LSI megaraid based
Chris Hoover wrote:
On Friday 23 April 2004 14:57, Ron St-Pierre wrote:
Does this apply to 7.3.4 also?
No it doesn't, I didn't look back through the thread far enough to see
what you were running. I tried it on 7.3.4 and none of the summary info
listed below was returned. FWIW one of our DBs
11 matches
Mail list logo
