Welcome!

Performance, Scalability and Architecture

Andreas Grabner

Subscribe to Andreas Grabner: eMailAlertsEmail Alerts
Get Andreas Grabner via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Andreas Grabner

Five SharePoint Deployment Performance Health Checks: Beyond Making Sure It's Running In my first blog I wrote about SharePoint System Performance Health Checks beyond looking at CPU and Memory Metrics. In this blog, I cover deployment related performance health problems that I always check when looking at a SharePoint Installation. Especially after deploying new hardware, new sites, pages, views, custom or third-party Web Parts (e.g., from AvePoint, K2, Nintex, Metalogix, etc.) it's important to perform certain deployment sanity checks. While you may have nobody reporting issues in the moment there are several areas that you constantly need to check before they become a real problem. Feel free to follow all my steps by either using your own tools or use Dynatrace Free Trial with our SharePoint FastPack. Step #1: Optimize Connectivity Between Services My first step... (more)

Performance Monitor All Your Apps By @Dynatrace | @DevOpsSummit [#DevOps]

How to Performance Monitor All Your Applications on a Single Dashboard It's become easy to monitor applications that are deployed on hundreds of servers - thanks to the advances in application performance management tools. But the more data you collect the harder it is to visualize the health state in a way that a single dashboard tells you both the overall status as well as the problematic component. Eugene Turetsky (Dynatrace) and Stephan Levesque (SSQ Financial Group) shared their solution for monitoring large IT infrastructures that contain several hundred components that sup... (more)

Software Quality Metrics For Continuous Delivery | @DevOpsSummit [#DevOps]

Software Quality Metrics for Your Continuous Delivery Pipeline | Part I How often do you deploy new software? Once a month, once a week or every hour? The more often you deploy the smaller your changes will be. That's good! Why? Because smaller changes tend to be less risky since it's easier to keep track of what has really changed. For developers, it's certainly easier to fix something you worked on three days ago than something you wrote last summer. An analogy from a recent conference talk from AutoScout24 is to think about your release like a container ship, and every one of y... (more)

Recursive Browser Redirect Loops | @DevOpsSummit [#DevOps]

Performance Impact of Recursive Browser Redirect Loops 100% Coverage I just recently wrote a blog about BOTs causing unwanted traffic on our servers. Right after I wrote this blog I was notified about yet another "interesting" and unusual load behavior on our download page which is used by customers to download latest product versions and updates: If you see such a load behavior you typically assume that you just released a new product version or maybe an update to our agents and many people are downloading it like crazy. Unfortunately that was not the case. The spike in traffic ... (more)

Don’t Trust Your Log Files | @DevOpsSummit [#DevOps]

Don’t Trust Your Log Files: How and Why to Monitor All Exceptions I would say that only one out of a million exceptions thrown in an application actually makes it to a log file - unless you run your application in verbose logging mode - Do you agree? No? Here is why I think that is: because most exceptions are handled by your code or by the frameworks your app uses. Here is a chart from an enterprise application showing that there are about 4000x more custom application exception objects thrown than important log messages written: 4000 times more Exceptions than log messages: Ca... (more)