The SQL monitor does use resources so this is not a surprise.
Unless there is a diagnosis of a problem going on I can't think of a reason
to run it all the time.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Friday, April 24, 2015 7:22 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Performance impact of SQL monitors
Recently got a contact from a coworker. Their SQL was running much slower
on an lpar. They keep detailed track of start/stop times of certain jobs
going back awhile. Their hypotheses was that someone was running an SQL
monitor. Yes, there was someone.
They duplicated the data on another lpar.
Ran SQL without any monitors running on system. Good performance.
Ran it again with an sql monitor running on something unrelated. Poor
performance.
Ran SQL again without any monitors running on system. Good performance.
Ran it again with an sql monitor running on something unrelated. Poor
performance.
These were all running in batch so it's not like "the first time this job
ran a certain process...".
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
