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

Are you developing or hosting PHP applications? Are you doing performance sanity checks along your delivery pipeline? No? Not Yet? Then start with a quick check. It only takes 15 minutes and it really pays off. As a developer you can improve your code, and as somebody responsible for your build pipeline you can automate these checks and enforce additional quality gates. And as a PHP Hosting company / group you will be able optimize your deployment and run more of these apps and sustain more load on the same infrastructure. Just like Java, .NET, and Ruby type applications, the top performance bottlenecks are fairly easy to spot and fixing them improves end user performance and saves compute power for your servers. Here is what we discovered when analyzing our own Moodle-based educational platform using the 15 Day Free Trial of dynaTrace: High PHP Compilation Time: O... (more)

Web Service Monitoring 101: Bad Deployments | @DevOpsSummit [#DevOps]

Web Service Monitoring 101: Identifying Bad Deployments Have you ever deployed a change to production and thought "All went well - Systems are operating as expected!" but then you had to deal with users complaining that they keep running into errors? When deployments fail you don't want your users to be the first to tell you about it: Sit down with the Business and Dev to define how and what to monitor We recently moved some of our systems between two of our data centers - even moving some components to the public cloud. Everything was prepared well, system monitoring was set u... (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)

Detecting Bad Deployments [#APM with #DevOps] | @DevOpsSummit

Detecting Bad Deployments on Resource Impact & Not Response Time This story came in from Joseph - one of our fellow dynaTrace users and a performance engineer at a large fleet management service company. Their fleet management software runs on .NET, is developed in-house, is load tested with JMeter and monitored in Production with dynaTrace. A usage and configuration change of their dependency injection library turned out to dramatically impact CPU and memory usage while not yet impacting end user experience. Lessons learned: resource usage monitoring is as important as response t... (more)