[gpfsug-discuss] Potential problems - leaving trace enabled in over-write mode?

[Oesterlin, Robert]

As always, Sven comes in to back this up with real data :)

To net this out, Sven – I should be able enable trace on my NSD servers running 4.2.2 without much impact, correct?

Bob Oesterlin
Sr Principal Storage Engineer, Nuance




From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Sven Oehme <oehmes at gmail.com>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Wednesday, March 8, 2017 at 7:37 AM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: [EXTERNAL] Re: [gpfsug-discuss] Potential problems - leaving trace enabled in over-write mode?

starting in version 3.4 we enhanced the trace code of scale significant. this went on release to release all the way up to 4.2.1. since 4.2.1 we made further improvements, but much smaller changes, more optimization , e.g. reducing of trace levels verbosity, etc .
with 4.2.2  we switched from blocking traces to in memory traces as the default trace infrastructure, this infrastructure was designed to be turned on all the time with minimal impact on performance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170308/c4f9d094/attachment.htm>