Expert insights. Personalized for you.
Dynatrace news. Modern service infrastructure depends heavily on IT’s ability to dynamically scale the number of hosts up or down, depending on the expected workload. MORE
By having appropriate indexes on your MySQL tables, you can greatly enhance the performance of SELECT queries. But, did you know that adding indexes to your tables in itself is an expensive operation, and may take a long time to complete depending on the size of your tables? MORE
Jim Keller recently gave a fascinating and far ranging interview on the AI Podcast. You can find it at Moore's Law, Microprocessors, Abstractions, and First Principles. One of the many topics of discussion was the often predicted death of Moore's Law. MORE
The CMG Impact conference (February 10-12, 2020 in Las Vegas) is coming. Looking at the program I have the same problem as I always had with CMG conferences – how could I attend all the sessions I want considering that we have multiple tracks? Even when I took out the sessions that don’t directly cover the topics of my primary interests as well as mainframe-specific presentations, I ended up with 21 sessions in 2.5 MORE
One of the quickest wins—and one of the first things I recommend my clients do—to make websites faster can at first seem counter-intuitive: you should self-host all of your static assets, forgoing others’ CDNs/infrastructure. MORE
Dynatrace news. Modern web applications rely heavily on Content Delivery Networks (CDNs) and 3rd-party integrations (for example, web analytics, tag managers, chat bots, A/B testing tools, ad providers, and more). MORE
It's time to automate you testing process! What Is Automated Testing? MORE
Dynatrace news. Modern microservices infrastructure commonly contain thousands of individual business-critical services and related dependencies. Managing highly dynamic service and application infrastructures with a CMDB database can be cumbersome and error prone. MORE
Dynatrace news. Businesses know that any service disruption can have detrimental business impact. MORE
I’m working on a client project at the moment and, as they’re an ecommerce site, there are a lot of facets of performance I’m keen to look into for them: load times are a good start, start render is key for customers who want to see information quickly (hint: that’s all of them), and client-specific metrics like how quickly did the key product image load? can all provide valuable insights. However, one metric I feel that front-end developers overlook all too quickly is Time to First Byte (TTFB). This is understandable—forgivable, almost—when you consider that TTFB begins to move into back-end territory, but if I was to sum up the problem as succinctly as possible, I’d say: While a good TTFB doesn’t necessarily mean you will have a fast website, a bad TTFB almost certainly guarantees a slow one. Even though, as a front-end developer, you might not be in the position to make improvements to TTFB yourself, it’s important to know that any problems with a high TTFB will leave you on the back foot, and any efforts you make to optimises images, clear the critical path, and asynchronously load your webfonts will all be made in the spirit of playing catchup. That’s not to say that more front-end oriented optimisations should be forgone, but there is, unfortunately, an air of closing the stable door after the horse has bolted. You really want to squish those TTFB bugs as soon as you can. What is TTFB? The TTFB timing entry isn’t particularly insightful. View full size/quality (375KB). TTFB is a little opaque to say the least. It comprises so many different things that I often think we tend to just gloss over it. A lot of people surmise that TTFB is merely time spent on the server, but that is only a small fraction of the true extent of things. The first—and often most surprising for people to learn—thing that I want to draw your attention to is that TTFB counts one whole round trip of latency. TTFB isn’t just time spent on the server, it is also the time spent getting from our device to the sever and back again (carrying, that’s right, the first byte of data!). Armed with this knowledge, we can soon understand why TTFB can often increase so dramatically on mobile. Surely, you’ve wondered before, the server has no idea that I’m on a mobile device—how can it be increasing its TTFB?! The reason is because mobile networks are, as a rule, high latency connections. If your Round Trip Time (RTT) from your phone to a server and back again is, say, 250ms, you’ll immediately see a corresponding increase in TTFB. If there is one key thing I’m keen for your to take from this post, its is that TTFB is affected by latency. But what else is TTFB? Strap yourself in; here is a non-exhaustive list presented in no particular order: Latency: As above, we’re counting a trip out to and a return trip from the server. A trip from a device in London to a server in New York has a theoretical best-case speed of 28ms over fibre, but this makes lots of very optimistic assumptions. Expect closer to 75ms. This is why serving your content from a CDN is so important: even in the internet age, being geographically closer to your customers is advantageous. Routing: If you are using a CDN—and you should be!—a customer in Leeds might get routed to the MAN datacentre. only to find that the resource they’re requesting isn’t in that PoP ’s cache. Accordingly, they’ll get routed all the way back to your origin server to retrieve it from there. If your origin is in, say, Virginia, that’s going to be a large and invisible increase in TTFB. Filesystem reads: The server simply reading static files such as images or sylesheets from the filesystem has a cost. It all gets added to your TTFB. Prioritisation: HTTP/2 has a (re)prioritisation mechanism whereby it may choose to stall lower-priority responses on the server while sending higher-priority responses down the wire. H/2 prioritisation issues aside, even when H/2 is running smoothly, these expected delays will contribute to your TTFB. Application runtime: It’s kind of obvious really, but the time it takes to run your actual application code is going to be a large contributor to your TTFB. Database queries: Pages that require data from a database will incur a cost when searching over it. More TTFB. API calls: If you need to call any APIs (internal or otherwise) in order to populate a page, the overhead will be counted in your TTFB. Server-Side Rendering: The cost of server-rendering a page could be trivial, but it will still contribute to your TTFB. Cheap hosting: Hosting that is optimised for cost over performance usually means you’re sharing a server with any number of other websites, so expect degraded server performance which could affect your ability to fulfil requests, or may simply mean underpowered hardware trying to run your application. DDoS or heavy load: In a similar vein to the previous point, increased load with no way of auto-scaling your application will lead to degraded performance where you begin to probe the limits of your infrastructure. WAFs and load balancers: Services such as web application firewalls or load balancers that sit in front of your application will also contribute to your TTFB. CDN features: Although a CDN is a huge net win, in certain scenarios, their features could lead to additional TTFB. For example, request collapsing , edge-side includes , etc.). Last-mile latency: When we think of a computer in London visiting a server in New York, we tend to oversimplify that journey quite drastically, almost imagining that the two were directly connected. The reality is that there’s a much more complex series of intermediaries from our own router to our ISP; from a cell tower to an undersea cable. Last mile latency deals with the disproportionate complexity toward the terminus of a connection. It’s impossible to have a 0ms TTFB, so it’s important to note that the list above does not represent things that are necessarily bad or slowing your TTFB down. Rather, your TTFB represents any number of the items present above. My aim here is not to point fingers at any particular part of the stack, but instead to help you understand what exactly TTFB can entail. And with so much potentially taking place in our TTFB phase, it’s almost a miracle that websites load at all! So. Much. Stuff! Demystifying TTFB. Thankfully, it’s not all so unclear anymore! With a little bit of extra work spent implementing the Server Timing API , we can begin to measure and surface intricate timings to the front-end, allowing web developers to identify and debug potential bottlenecks previously obscured from view. The Server Timing API allows developers to augment their responses with an additional Server-Timing HTTP header which contains timing information that the application has measured itself. This is exactly what we did at BBC iPlayer last year: The newly-available Server-Timing header can be added to any response. View full size/quality (533KB). N.B. Server Timing doesn’t come for free: you need to actually measure the aspects listed above yourself and then populate your Server-Timing header with the relevant data. All the browser does is display the data in the relevant tooling, making it available on the front-end: Now we can see, right there in the browser, how long certain aspects of our TTFB took. View full size/quality (419KB). To help you get started, Christopher Sidebottom wrote up his implementation of the Server Timing API. during our time optimising iPlayer. It’s vital that we understand just what TTFB can cover, and just how critical it can be to overall performance. TTFB has knock-on effects, which can be a good thing or a bad thing depending on whether it’s starting off low or high. If you’re slow out of the gate, you’ll spend the rest of the race playing catchup. MORE
Despite having been called CSS Wizardry for over a decade now, there hasn’t been a great deal of CSS-related content on this site for a while. Let me address that by combining my two favourite topics: CSS and performance. MORE
In a MySQL master-slave high availability (HA) setup, it is important to continuously monitor the health of the master and slave servers so you can detect potential issues and take corrective actions. In this blog post, we explain some basic health checks you can do on your MySQL master and slave nodes to ensure your setup is healthy. MORE
In our previous blog posts, we discussed the capabilities and functioning of PostgreSQL Automatic Failover (PAF) by Cluster Labs and Replication Manager (repmgr) by 2ndQuadrant. In the final post of this series, we will review the last solution, Patroni by Zalando, and compare all three at the end so you can determine which high availability framework is best for your PostgreSQL hosting deployment. Managing High Availability in PostgreSQL – Part I: PostgreSQL Automatic Failover. MORE
The projections are in! Check out these testing trends! The software development landscape continues to evolve with DevOps and Agile development methods taking over traditional approaches. The advent of these methods has led to the innovation and use of new testing techniques. MORE
I am looking forward to share my thoughts on ‘Reinventing Performance Testing’ at the imPACt performance and capacity conference by CMG held on November 7-10, 2016 in La Jolla, CA. I decided to publish a few parts here to see if anything triggers a discussion. It would be published as separate posts: – Introduction (a short teaser). – Cloud. – Agile. Continuous Integration (this post). – New Architectures. – New Technologies. MORE
C10K problem is a term that stands for ten thousand concurrently handling connections. MORE
I am looking forward to share my thoughts on ‘Reinventing Performance Testing’ at the imPACt performance and capacity conference by CMG held on November 7-10, 2016 in La Jolla, CA. I decided to publish a few parts here to see if anything triggers a discussion. It would be published as separate posts: – Introduction (a short teaser). – Cloud. – Agile. – Continuous Integration. New Architectures (this post). – New Technologies. MORE
I am looking forward to share my thoughts on ‘Reinventing Performance Testing’ at the imPACt performance and capacity conference by CMG held on November 7-10, 2016 in La Jolla, CA. I decided to publish a few parts here to see if anything triggers a discussion. It would be published as separate posts: – Introduction (a short teaser). – Cloud. Agile (this post). – Continuous Integration. – New Architectures. – New Technologies. MORE
There was a rather heated discussion around A Context-Driven Approach to Automation in Testing by James Bach and Michael Bolton (referred below as the article and the authors – other references would be explicit). Here are a couple of places where it got fiercely attacked Reviewing “Context Driven Approach to Automation in Testing” by Chris McMahon. and Open letter to “CDT Test Automation” reviewers as well as in many other different places. MORE
We’ve seen many of the technological advances described in the Star Trek milieu become reality over the last 50 years, from personal communication devices and instant translators to GMOs, medical robots, 3D printing and weapons that stun. But, ah yes, the matter transporter. MORE
I am very excited by the upcoming CMG imPACt performance and capacity conference. This year it would be held on November 6-9, 2017 in New Orleans, LA. It is only such vendor-neutral, 4-day, 5-track conference devoted completely to performance, capacity, scalability, and adjacent topics. It is organized by CMG (Computer Measurement Group) , a not-for-profit, worldwide organization of performance and capacity planning professionals. MORE
Wake up! It's HighScalability time: Visualize the huge scale of Deep Time by identifying key reference points along the way. Do you like this sort of Stuff? Without your support on Patreon Stuff won't happen. MORE
I am looking forward to share my thoughts on ‘Reinventing Performance Testing’ at the imPACt performance and capacity conference by CMG held on November 7-10, 2016 in La Jolla, CA. I decided to publish a few parts here to see if anything triggers a discussion. MORE
Quality Assurance (QA) is at the point of inflection and it is an exciting time to be in the field of QA as advanced digital technologies are influencing QA practices. MORE
Essential Suite?—?Artwork Artwork Producer Assistant By: Hamid Shahid & Syed Haq Introduction Netflix continues to invest in content for a global audience with a diverse range of unique tastes and interests. MORE
An interesting discussion started around a very good post Open Source Load Testing Tool Review by Ragnar Lönn. Somehow the latest comment, which I got in my e-mail, didn’t get published. So I decided to copy the discussion as is and publish the comment (and my answer) here. Check the original post (as well as many other great posts) following the link above – but the discussion below is somewhat independent. MORE
I was honored to write a preface to the great new book Master Apache JMeter. From load testing to DevOps. Here it is: An important event, directly related to this book, happened recently and probably went unnoticed. It appears that Apache JMeter became the most popular load testing tool. MORE
Dynatrace news. Traditionally, it’s critical for Dev and Ops teams to be able to quickly discover and remediate application performance and customer-facing issues. MORE
Dynatrace news. The timeframe selector is one of the most widely used UI controls in Dynatrace. MORE
Dynatrace news. Deployment of OneAgent is really easy. You just run the installer—no parameter configurations required—and OneAgent takes care of the rest. MORE
One software vendor ask me, along with a few other performance professionals, to answer questions related to performance trends. But they changed their mind and never published it – leaving me to contemplate which particular thought they didn’t like… Well, here are their questions and my answers: What do you think is the “next big thing in performance” – or what should we all keep an eye out for in 2018? MORE
Disclaimers: I was not approached or hired by Hoefler&Co or Cloud.typography to look into any of the following issues. I disclosed all of the below to Cloud.typography and gave them ample opportunity to work together to solve the issues at the root of the problem. MORE
Dynatrace news. Dynatrace helps you monitor hyper-complex environments where tribal knowledge about entities and their relationships isn’t sufficient. To achieve this, Dynatrace provides important components such as OneAgent and ActiveGate. MORE
Guest Post by Wendy Dessler. Source- Pixabay. When trying to develop a new piece of software or an app, one of the first things a developer has to do is pick a programming language. For years, the debate has raged on regarding which programming language is better, Java or Scala. MORE
by Artem Shtatnov and Ravi Srinivas Ranganathan Almost a year ago we described our learnings from adopting GraphQL on the Netflix Marketing Tech team. We have a lot more to share since then! MORE
Dynatrace news. Autonomous Cloud is not another lofty marketing term. Autonomous Cloud is what enables our globally distributed development teams at Dynatrace to deliver better software faster following our NoOps approach: Fully Autonomous and as a Self-Service! MORE
My post Good Times for Load Testing was published in 2014. It is difficult to believe that 5 years passed… Are times still good for load testing? Well, yes and no. I am not so upbeat as I was in 2014. MORE
One of the key tools that performance engineers have at their disposal is the Performance Budget: it helps us—or, more importantly, our clients—ensure that any performance-focused work is monitored and maintained after we’ve gone. MORE
In a MySQL master-slave high availability (HA) setup, it is important to continuously monitor the health of the master and slave servers so you can detect potential issues and take corrective actions. In this blog post, we explain some basic health checks you can do on your MySQL master and slave nodes to ensure your setup is healthy. MORE
Dynatrace news. Across both his day one and day two mainstage presentations, Steve Tack, SVP of Product Management, described some of the investments we’re making to continue to differentiate the Dynatrace Software Intelligence Platform. MORE
This is the second article that describes how to test asynchronous operations with the Byteman framework in an application using the Spring framework. MORE
Dynatrace news. In Part 1 of this blog series , we presented a few Dynatrace customer use cases for multidimensional analysis. MORE
Toby Mao , Sri Sri Perangur , Colin McFarland Another day, another custom script to analyze an A/B test. Maybe you’ve done this before and have an old script lying around. If it’s new, it’s probably going to take some time to set up, right? Not at Netflix. MORE
Following up my post Are Times still Good for Load Testing? , I decided to answer multiple comments here separately. First, I’d like to elaborate on “It may be less need for simple load testing due to increased scale and sophistication of systems” I meant that the traditional way – testing the system before deploying in production using production-type workload – is not the only way anymore. MORE
Alex Podelko
JUNE 12, 2019
My post Good Times for Load Testing was published in 2014. It is difficult to believe that 5 years passed… Are times still good for load testing? Well, yes and no. I am not so upbeat as I was in 2014.
Alex Podelko
AUGUST 18, 2019
Following up my post Are Times still Good for Load Testing? , I decided to answer multiple comments here separately. First, I’d like to elaborate on “It may be less need for simple load testing due to increased scale and sophistication of systems” I meant that the traditional way – testing the system before deploying in production using production-type workload – is not the only way anymore.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Alex Podelko
DECEMBER 19, 2019
The CMG Impact conference (February 10-12, 2020 in Las Vegas) is coming. Looking at the program I have the same problem as I always had with CMG conferences – how could I attend all the sessions I want considering that we have multiple tracks? Even when I took out the sessions that don’t directly cover the topics of my primary interests as well as mainframe-specific presentations, I ended up with 21 sessions in 2.5
Alex Podelko
NOVEMBER 21, 2018
I was honored to write a preface to the great new book Master Apache JMeter. From load testing to DevOps. Here it is: An important event, directly related to this book, happened recently and probably went unnoticed. It appears that Apache JMeter became the most popular load testing tool.
Alex Podelko
SEPTEMBER 4, 2018
Guest Post by Wendy Dessler. Source- Pixabay. When trying to develop a new piece of software or an app, one of the first things a developer has to do is pick a programming language. For years, the debate has raged on regarding which programming language is better, Java or Scala.
Alex Podelko
JULY 13, 2018
One software vendor ask me, along with a few other performance professionals, to answer questions related to performance trends. But they changed their mind and never published it – leaving me to contemplate which particular thought they didn’t like… Well, here are their questions and my answers: What do you think is the “next big thing in performance” – or what should we all keep an eye out for in 2018?
Alex Podelko
OCTOBER 28, 2016
I am looking forward to share my thoughts on ‘Reinventing Performance Testing’ at the imPACt performance and capacity conference by CMG held on November 7-10, 2016 in La Jolla, CA. I decided to publish a few parts here to see if anything triggers a discussion.
Alex Podelko
AUGUST 24, 2017
There was a rather heated discussion around A Context-Driven Approach to Automation in Testing by James Bach and Michael Bolton (referred below as the article and the authors – other references would be explicit). Here are a couple of places where it got fiercely attacked Reviewing “Context Driven Approach to Automation in Testing” by Chris McMahon. and Open letter to “CDT Test Automation” reviewers as well as in many other different places.
Alex Podelko
AUGUST 15, 2017
An interesting discussion started around a very good post Open Source Load Testing Tool Review by Ragnar Lönn. Somehow the latest comment, which I got in my e-mail, didn’t get published. So I decided to copy the discussion as is and publish the comment (and my answer) here. Check the original post (as well as many other great posts) following the link above – but the discussion below is somewhat independent.
Alex Podelko
OCTOBER 20, 2016
I am looking forward to share my thoughts on ‘Reinventing Performance Testing’ at the imPACt performance and capacity conference by CMG held on November 7-10, 2016 in La Jolla, CA. I decided to publish a few parts here to see if anything triggers a discussion. It would be published as separate posts: – Introduction (a short teaser). – Cloud. – Agile. – Continuous Integration. New Architectures (this post). – New Technologies.
Alex Podelko
OCTOBER 18, 2016
I am looking forward to share my thoughts on ‘Reinventing Performance Testing’ at the imPACt performance and capacity conference by CMG held on November 7-10, 2016 in La Jolla, CA. I decided to publish a few parts here to see if anything triggers a discussion. It would be published as separate posts: – Introduction (a short teaser). – Cloud. – Agile. Continuous Integration (this post). – New Architectures. – New Technologies.
Alex Podelko
OCTOBER 13, 2016
I am looking forward to share my thoughts on ‘Reinventing Performance Testing’ at the imPACt performance and capacity conference by CMG held on November 7-10, 2016 in La Jolla, CA. I decided to publish a few parts here to see if anything triggers a discussion. It would be published as separate posts: – Introduction (a short teaser). – Cloud. Agile (this post). – Continuous Integration. – New Architectures. – New Technologies.
DZone
FEBRUARY 14, 2020
We’ve seen many of the technological advances described in the Star Trek milieu become reality over the last 50 years, from personal communication devices and instant translators to GMOs, medical robots, 3D printing and weapons that stun. But, ah yes, the matter transporter.
CSS Wizardry
AUGUST 7, 2019
I’m working on a client project at the moment and, as they’re an ecommerce site, there are a lot of facets of performance I’m keen to look into for them: load times are a good start, start render is key for customers who want to see information quickly (hint: that’s all of them), and client-specific metrics like how quickly did the key product image load? can all provide valuable insights. However, one metric I feel that front-end developers overlook all too quickly is Time to First Byte (TTFB). This is understandable—forgivable, almost—when you consider that TTFB begins to move into back-end territory, but if I was to sum up the problem as succinctly as possible, I’d say: While a good TTFB doesn’t necessarily mean you will have a fast website, a bad TTFB almost certainly guarantees a slow one. Even though, as a front-end developer, you might not be in the position to make improvements to TTFB yourself, it’s important to know that any problems with a high TTFB will leave you on the back foot, and any efforts you make to optimises images, clear the critical path, and asynchronously load your webfonts will all be made in the spirit of playing catchup. That’s not to say that more front-end oriented optimisations should be forgone, but there is, unfortunately, an air of closing the stable door after the horse has bolted. You really want to squish those TTFB bugs as soon as you can. What is TTFB? The TTFB timing entry isn’t particularly insightful. View full size/quality (375KB). TTFB is a little opaque to say the least. It comprises so many different things that I often think we tend to just gloss over it. A lot of people surmise that TTFB is merely time spent on the server, but that is only a small fraction of the true extent of things. The first—and often most surprising for people to learn—thing that I want to draw your attention to is that TTFB counts one whole round trip of latency. TTFB isn’t just time spent on the server, it is also the time spent getting from our device to the sever and back again (carrying, that’s right, the first byte of data!). Armed with this knowledge, we can soon understand why TTFB can often increase so dramatically on mobile. Surely, you’ve wondered before, the server has no idea that I’m on a mobile device—how can it be increasing its TTFB?! The reason is because mobile networks are, as a rule, high latency connections. If your Round Trip Time (RTT) from your phone to a server and back again is, say, 250ms, you’ll immediately see a corresponding increase in TTFB. If there is one key thing I’m keen for your to take from this post, its is that TTFB is affected by latency. But what else is TTFB? Strap yourself in; here is a non-exhaustive list presented in no particular order: Latency: As above, we’re counting a trip out to and a return trip from the server. A trip from a device in London to a server in New York has a theoretical best-case speed of 28ms over fibre, but this makes lots of very optimistic assumptions. Expect closer to 75ms. This is why serving your content from a CDN is so important: even in the internet age, being geographically closer to your customers is advantageous. Routing: If you are using a CDN—and you should be!—a customer in Leeds might get routed to the MAN datacentre. only to find that the resource they’re requesting isn’t in that PoP ’s cache. Accordingly, they’ll get routed all the way back to your origin server to retrieve it from there. If your origin is in, say, Virginia, that’s going to be a large and invisible increase in TTFB. Filesystem reads: The server simply reading static files such as images or sylesheets from the filesystem has a cost. It all gets added to your TTFB. Prioritisation: HTTP/2 has a (re)prioritisation mechanism whereby it may choose to stall lower-priority responses on the server while sending higher-priority responses down the wire. H/2 prioritisation issues aside, even when H/2 is running smoothly, these expected delays will contribute to your TTFB. Application runtime: It’s kind of obvious really, but the time it takes to run your actual application code is going to be a large contributor to your TTFB. Database queries: Pages that require data from a database will incur a cost when searching over it. More TTFB. API calls: If you need to call any APIs (internal or otherwise) in order to populate a page, the overhead will be counted in your TTFB. Server-Side Rendering: The cost of server-rendering a page could be trivial, but it will still contribute to your TTFB. Cheap hosting: Hosting that is optimised for cost over performance usually means you’re sharing a server with any number of other websites, so expect degraded server performance which could affect your ability to fulfil requests, or may simply mean underpowered hardware trying to run your application. DDoS or heavy load: In a similar vein to the previous point, increased load with no way of auto-scaling your application will lead to degraded performance where you begin to probe the limits of your infrastructure. WAFs and load balancers: Services such as web application firewalls or load balancers that sit in front of your application will also contribute to your TTFB. CDN features: Although a CDN is a huge net win, in certain scenarios, their features could lead to additional TTFB. For example, request collapsing , edge-side includes , etc.). Last-mile latency: When we think of a computer in London visiting a server in New York, we tend to oversimplify that journey quite drastically, almost imagining that the two were directly connected. The reality is that there’s a much more complex series of intermediaries from our own router to our ISP; from a cell tower to an undersea cable. Last mile latency deals with the disproportionate complexity toward the terminus of a connection. It’s impossible to have a 0ms TTFB, so it’s important to note that the list above does not represent things that are necessarily bad or slowing your TTFB down. Rather, your TTFB represents any number of the items present above. My aim here is not to point fingers at any particular part of the stack, but instead to help you understand what exactly TTFB can entail. And with so much potentially taking place in our TTFB phase, it’s almost a miracle that websites load at all! So. Much. Stuff! Demystifying TTFB. Thankfully, it’s not all so unclear anymore! With a little bit of extra work spent implementing the Server Timing API , we can begin to measure and surface intricate timings to the front-end, allowing web developers to identify and debug potential bottlenecks previously obscured from view. The Server Timing API allows developers to augment their responses with an additional Server-Timing HTTP header which contains timing information that the application has measured itself. This is exactly what we did at BBC iPlayer last year: The newly-available Server-Timing header can be added to any response. View full size/quality (533KB). N.B. Server Timing doesn’t come for free: you need to actually measure the aspects listed above yourself and then populate your Server-Timing header with the relevant data. All the browser does is display the data in the relevant tooling, making it available on the front-end: Now we can see, right there in the browser, how long certain aspects of our TTFB took. View full size/quality (419KB). To help you get started, Christopher Sidebottom wrote up his implementation of the Server Timing API. during our time optimising iPlayer. It’s vital that we understand just what TTFB can cover, and just how critical it can be to overall performance. TTFB has knock-on effects, which can be a good thing or a bad thing depending on whether it’s starting off low or high. If you’re slow out of the gate, you’ll spend the rest of the race playing catchup.
Scalegrid
NOVEMBER 20, 2019
By having appropriate indexes on your MySQL tables, you can greatly enhance the performance of SELECT queries. But, did you know that adding indexes to your tables in itself is an expensive operation, and may take a long time to complete depending on the size of your tables?
CSS Wizardry
MAY 31, 2019
One of the quickest wins—and one of the first things I recommend my clients do—to make websites faster can at first seem counter-intuitive: you should self-host all of your static assets, forgoing others’ CDNs/infrastructure.
Dynatrace
FEBRUARY 20, 2020
Dynatrace news. Modern service infrastructure depends heavily on IT’s ability to dynamically scale the number of hosts up or down, depending on the expected workload.
Dynatrace
FEBRUARY 19, 2020
Dynatrace news. The timeframe selector is one of the most widely used UI controls in Dynatrace.
Scalegrid
FEBRUARY 17, 2020
In a MySQL master-slave high availability (HA) setup, it is important to continuously monitor the health of the master and slave servers so you can detect potential issues and take corrective actions. In this blog post, we explain some basic health checks you can do on your MySQL master and slave nodes to ensure your setup is healthy.
Dynatrace
FEBRUARY 18, 2020
Dynatrace news. Traditionally, it’s critical for Dev and Ops teams to be able to quickly discover and remediate application performance and customer-facing issues.
CSS Wizardry
JANUARY 8, 2020
One of the key tools that performance engineers have at their disposal is the Performance Budget: it helps us—or, more importantly, our clients—ensure that any performance-focused work is monitored and maintained after we’ve gone.
High Scalability
FEBRUARY 17, 2020
In a MySQL master-slave high availability (HA) setup, it is important to continuously monitor the health of the master and slave servers so you can detect potential issues and take corrective actions. In this blog post, we explain some basic health checks you can do on your MySQL master and slave nodes to ensure your setup is healthy.
DZone
JANUARY 31, 2020
C10K problem is a term that stands for ten thousand concurrently handling connections.
High Scalability
FEBRUARY 19, 2020
Jim Keller recently gave a fascinating and far ranging interview on the AI Podcast. You can find it at Moore's Law, Microprocessors, Abstractions, and First Principles. One of the many topics of discussion was the often predicted death of Moore's Law.
DZone
NOVEMBER 21, 2019
It's time to automate you testing process! What Is Automated Testing?
CSS Wizardry
AUGUST 13, 2019
Disclaimers: I was not approached or hired by Hoefler&Co or Cloud.typography to look into any of the following issues. I disclosed all of the below to Cloud.typography and gave them ample opportunity to work together to solve the issues at the root of the problem.
The Netflix TechBlog
NOVEMBER 4, 2019
by Artem Shtatnov and Ravi Srinivas Ranganathan Almost a year ago we described our learnings from adopting GraphQL on the Netflix Marketing Tech team. We have a lot more to share since then!
CSS Wizardry
NOVEMBER 9, 2018
Despite having been called CSS Wizardry for over a decade now, there hasn’t been a great deal of CSS-related content on this site for a while. Let me address that by combining my two favourite topics: CSS and performance.
DZone
FEBRUARY 14, 2020
Quality Assurance (QA) is at the point of inflection and it is an exciting time to be in the field of QA as advanced digital technologies are influencing QA practices.
Dynatrace
FEBRUARY 11, 2020
Dynatrace news. Deployment of OneAgent is really easy. You just run the installer—no parameter configurations required—and OneAgent takes care of the rest.
Dynatrace
FEBRUARY 1, 2020
Dynatrace news. Modern web applications rely heavily on Content Delivery Networks (CDNs) and 3rd-party integrations (for example, web analytics, tag managers, chat bots, A/B testing tools, ad providers, and more).
Dynatrace
FEBRUARY 12, 2020
Dynatrace news. Dynatrace helps you monitor hyper-complex environments where tribal knowledge about entities and their relationships isn’t sufficient. To achieve this, Dynatrace provides important components such as OneAgent and ActiveGate.
DZone
FEBRUARY 13, 2020
This is the second article that describes how to test asynchronous operations with the Byteman framework in an application using the Spring framework.
Dynatrace
FEBRUARY 6, 2020
Dynatrace news. Autonomous Cloud is not another lofty marketing term. Autonomous Cloud is what enables our globally distributed development teams at Dynatrace to deliver better software faster following our NoOps approach: Fully Autonomous and as a Self-Service!
DZone
JANUARY 7, 2020
The projections are in! Check out these testing trends! The software development landscape continues to evolve with DevOps and Agile development methods taking over traditional approaches. The advent of these methods has led to the innovation and use of new testing techniques.
Dynatrace
FEBRUARY 13, 2020
Dynatrace news. Across both his day one and day two mainstage presentations, Steve Tack, SVP of Product Management, described some of the investments we’re making to continue to differentiate the Dynatrace Software Intelligence Platform.
High Scalability
FEBRUARY 14, 2020
Wake up! It's HighScalability time: Visualize the huge scale of Deep Time by identifying key reference points along the way. Do you like this sort of Stuff? Without your support on Patreon Stuff won't happen.
The Netflix TechBlog
SEPTEMBER 10, 2019
Toby Mao , Sri Sri Perangur , Colin McFarland Another day, another custom script to analyze an A/B test. Maybe you’ve done this before and have an old script lying around. If it’s new, it’s probably going to take some time to set up, right? Not at Netflix.
The Netflix TechBlog
FEBRUARY 14, 2020
Essential Suite?—?Artwork Artwork Producer Assistant By: Hamid Shahid & Syed Haq Introduction Netflix continues to invest in content for a global audience with a diverse range of unique tastes and interests.
Dynatrace
FEBRUARY 14, 2020
Dynatrace news. Businesses know that any service disruption can have detrimental business impact.
Dynatrace
FEBRUARY 14, 2020
Dynatrace news. Modern microservices infrastructure commonly contain thousands of individual business-critical services and related dependencies. Managing highly dynamic service and application infrastructures with a CMDB database can be cumbersome and error prone.
Dynatrace
FEBRUARY 5, 2020
Dynatrace news. In Part 1 of this blog series , we presented a few Dynatrace customer use cases for multidimensional analysis.
Scalegrid
AUGUST 22, 2019
In our previous blog posts, we discussed the capabilities and functioning of PostgreSQL Automatic Failover (PAF) by Cluster Labs and Replication Manager (repmgr) by 2ndQuadrant. In the final post of this series, we will review the last solution, Patroni by Zalando, and compare all three at the end so you can determine which high availability framework is best for your PostgreSQL hosting deployment. Managing High Availability in PostgreSQL – Part I: PostgreSQL Automatic Failover.
154 
Let's personalize your content