Archives of the TeradataForum

Message Posted: Fri, 18 Jul 2003 @ 13:37:05 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Patrick,

We've been doing this for some time. We're on V2R4.1 so we don't have the overall system limiter that priority scheduler now has. Therefore we run a heavy query in a partition which is capped by an ABS policy.

Originally it worked well but when we upgraded from a 5250 with EMC disks to a 5350 with (faster) LSI disks we found the previous query didn't produce the right effect. Since then we've found it difficult to get a new query with proof of the right balance between CPU & I/O. Bear in mind that ABS caps CPU only.

The end result is that we have a slightly modified query running in a 20% ABS AG and schmon shows this usually uses 24% of the CPU, which is our aim. The amount of I/O being measured differs according to what you use to measure it with, e.g. schmon or PMON, so that aspect of the throttling is confused still but we're happy with the situation.

Regards,

John

	<Prev	Next>		<<First	<Prev	Next>	Last>>