RE: Heisenberg and measurement intrusion....
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxx>, "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 31 Jul 2007 13:20:23 -0700
That depends on exactly what you mean by "monitoring"? If you're just
talking about taking a snapshot (e.g. with statspack) before and after
the baseline, then there isn't any overhead during the monitored period.
If you're talking about monitoring by constantly running queries against
v$sql, v$session, v$sesstat and running sar, iostat, vmstat, etc. during
the baseline, then those could certainly have an impact on the
performance so they should either be eliminated or accounted for. It
also depends on if your "monitoring" is a constant, integral part of the
environment (e.g. 10g AWR/ASH/ADDM), in which case it shouldn't be
eliminated during your baseline, or if your monitoring is some ad-hoc
utilities and queries that you only run under certain circumstances.
Regards,
Brandon
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Ted Coyle
Is the statement below accurate?
"So the Heisenberg uncertainty principle mandates we run without
monitoring as a baseline."
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
