Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: how can a couple of expensive queries drag my system down?




is this 'normal'? (loaded question I know)

Depends. If you are on the edge, disk-wise, yes a big fat query can push it over and make it fall.

Should I be looking to offload expensive reporting queries to read-only
replicants of my database?

You could do this, especially if the heavy queries involve reading gigabytes of data from disk (as reporting queries like to do). In that case, you can even use a cheap machine with cheap disks for the slave (even striped RAID) since data is duplicated anyway and all that matters is megabytes/second, not IOs/second.

Is this a symptom of slow disk?

	vmstat will tell you this.
	If iowait time goes through the roof, yes it's disk bound.
	If cpu use goes 100%, then it's cpu bound.

imporoperly tuned postgres settings? bad

	Also possible, you can try EXPLAIN of the problematic queries.

choice of OS, hardware, storage?

	Depends on how your SAN handles load. No idea about that.

Is this a sign of disk contention?

	Most probable.

How does CPU load come into play?

	With 8 CPUs, less likely.
(Your problem query can swamp at most 1 CPU, so if the machine grinds with still 7 other cores available for the usual, it probably isn't cpu-bound)




Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group