|
Archives of the TeradataForumMessage Posted: Thu, 06 Jul 2006 @ 19:23:49 GMT
Hi, I am testing Priority Scheduler at the moment. As you can see on the schmon script below, I have set some query milestones for the ressource partition 3. schmon -l 100 schmon -w 0 80 schmon -b 0 Default 100 100 schmon -b 1 Query 90 100 schmon -b 2 Batch 10 100 schmon -b 3 General 90 100 schmon -a 1 N 5 100 schmon -a 2 N 10 100 schmon -a 3 N 20 100 schmon -a 4 N 40 100 schmon -a 11 N 5 100 schmon -a 12 N 10 100 schmon -a 13 N 20 100 schmon -a 14 N 40 100 schmon -a 21 N 5 100 schmon -a 22 N 10 100 schmon -a 23 N 20 100 schmon -a 24 N 40 100 schmon -a 31 N 10 100 schmon -a 32 N 20 100 schmon -a 33 N 40 100 schmon -a 34 N 80 100 schmon -p 0 L 0 R 0.00 1 schmon -p 1 M 0 R 0.00 2 schmon -p 2 H 0 R 0.00 3 schmon -p 3 R 0 R 0.00 4 schmon -p 4 L1 1 R 0.00 11 schmon -p 5 M1 1 R 0.00 12 schmon -p 6 H1 1 R 0.00 13 schmon -p 7 R1 1 R 0.00 14 schmon -p 8 L2 2 R 0.00 21 schmon -p 9 M2 2 R 0.00 22 schmon -p 10 H2 2 R 0.00 23 schmon -p 11 R2 2 R 0.00 24 schmon -p 12 L3 3 Q 0.00 31 schmon -p 13 M3 3 Q 600.00 32 0.00 31 schmon -p 14 H3 3 Q 5.00 33 0.00 32 schmon -p 15 R3 3 Q 1.00 34 0.00 33 So, using a user with the account R3, I launch a query that takes about 5 minutes to run. While the query run, I can see(schmon -m) that the first Performance Group used is R3, then switch to H3, but never goes to M3. As per my comprehension, after 5 seconds, the query is suppose to switch to M3. This is not the case. Even after 5 minutes, it stays on the H3 Performance Group and so til the end. Is anybody can explain me what I'm doing wrong or what I don't understand? Any help would be really appreciated. Mario
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||