January 24, 2022 at 12:00 am
Comments posted to this topic are about the item Knowing When to Respond
January 24, 2022 at 2:43 pm
Monitoring your apps to get a baseline is a great idea. It's one that I wish I'd been a part of but haven't ever been. At my old job there were sometimes when the web app providers used to enter billing services appeared to be running slow. Or so they said. It was a small IT shop, where the two of us wore several hats. But neither of us had network skills, so we didn't know what to do. Sometimes we could tweak a page to improve performance, but other times the best we could do was hope it went away.
In my current job the IT shop is much larger. There are networking people, etc. Occasionally I'll hear something running slow, but I think it's handled most of the time it's handled by someone in Ops. I've no idea what they do, whether they monitor systems and develop baselines or if they just react to what's happening at the moment.
Kindest Regards, Rod Connect with me on LinkedIn.
January 24, 2022 at 7:44 pm
Query Store is a good tool for baselining a query over time and also identifying if it's execution plan has regressed in a way that contributes to it's performance. Too bad it can't be enabled on AOG secondaries, because that's where most of our applications execute queries.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 25, 2022 at 7:33 pm
From the Article:
"Without a baseline, every issue encountered could be considered normal and therefore not require any additional intervention."
Another way to look at it is "Without a baseline, every non-issue encountered could be be considered to be an emergency and therefore require constant, urgent, totally unnecessary intervention".
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply