Fri.Jul 26, 2019

article thumbnail

How to Build a Distributed Load Testing Infrastructure with AWS, Docker, and JMeter

DZone

Before we get into the tutorial hands-on, I would like to mention that this topic is not new. It has been covered in various helpful articles like the ones from TestAutomationGuru. The content which I am about to present has its custom favors and solves specific issues that I have encountered while working with this setup.

article thumbnail

We Love Speed 2019 on September 20 in Lille

Dareboost

After a most successful 2018 edition, Dareboost is proud to keep sponsoring the French Web Performance event: We Love Speed.

Speed 76
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Troubleshooting the Performance of Vert.x Applications, Part II - Preventing Event Loop Delays

DZone

In the previous part of the series, we took a closer look at the event loop model. In this article, we are going to discuss several techniques that help you to prevent event loop delays. The causes of event loop delays can be divided into two categories. The first category contains event loop delays caused by a handler calling a blocking API. The second category covers delays caused by a handler code taking a great amount of CPU time to complete.

article thumbnail

Max Worker Threads for SQL Server Always on Availability Group databases

SQL Shack

This article gives an overview of the Max Worker Threads for the SQL Server Always On Availability Group databases. SQL Server Always On Availability Group is a widely accepted feature to implement high availability and disaster recovery solution (HADR). It is available from SQL Server 2012 onwards. Please make sure you have good knowledge of […].

article thumbnail

Stuff The Internet Says On Scalability For July 26th, 2019

High Scalability

Wake up! It's HighScalability time—once again: The Apollo 11 guidance computer repeatedly crashed on descent. On earth computer scientists had just 13 hours to debug the problem. They did. It was CPU overload because of a wrong setting. Some things never change! Do you like this sort of Stuff? I'd greatly appreciate your support on Patreon. I wrote Explain the Cloud Like I'm 10 for people who need to understand the cloud.