Brendan Gregg

FEBRUARY 28, 2023

My personal opinion is that I don't see a widespread need for more capacity given horizontal scaling and servers that can already exceed 1 Tbyte of DRAM; bandwidth is also helpful, but I'd be concerned about the increased latency for adding a hop to more memory.

Performance 110

Performance Latency Cache Virtualization 110

SQL Performance

JULY 16, 2019

A close monitoring of the hardware enthusiast community, including many of the most respected hardware analysts and reviewers paints an even more dire picture about Intel in the server processor space. Despite all of this, Intel is not going to lose their entire server processor business any time soon.

Servers 46

Servers Hardware Architecture Retail 46

SQL Performance

JUNE 21, 2019

I've been teaching and writing about common SQL Server mistakes for many years. This article will expand on my previous article and point out how these apply to SQL Server , Azure SQL Database , and Azure SQL Managed Instance. SQL Server Agent alerts. This situation applies to on-premises SQL Server and IaaS. Statistics.

Servers 49

Servers Azure Hardware Database 49

Brendan Gregg

FEBRUARY 28, 2023

My personal opinion is that I don't see a widespread need for more capacity given horizontal scaling and servers that can already exceed 1 Tbyte of DRAM; bandwidth is also helpful, but I'd be concerned about the increased latency for adding a hop to more memory. That's about 24 hours from now!

Performance 52

Performance Latency Cache Virtualization 52

SQL Server According to Bob

JUNE 3, 2016

SQL Server 2016 ‘It Just Runs Faster’ A bold statement that any SQL Server professional can stand behind with confidence. Try SQL Server 2016 Today. The SQL Server Development team tasked several individuals with scalability improvements and real world testing patterns. – [link]. Auto-soft NUMA. . ….

Hardware 40

Hardware Software Engineering Transportation Scalability 40

Randon ASCII

FEBRUARY 25, 2018

In this particular investigation, which spanned twenty months, we suspected hardware failure, compiler bugs, linker bugs, and other possibilities. Jumping too quickly to blaming hardware or build tools is a classic mistake, but in this case the mistake was that we weren’t thinking big enough.

Programming 79

Programming Hardware Cache Code 79