Remove 2015 Remove Cache Remove Database Remove Hardware
article thumbnail

Using Parallel Query with Amazon Aurora for MySQL

Percona

On multi-core machines – which is the majority of the hardware nowadays – and in the cloud, we have multiple cores available for use. Aurora Parallel Query response time (for queries which can not use indexes) can be 5x-10x better compared to the non-parallel fully cached operations. The second and third run used the cached data.

Cache 47
article thumbnail

SQL 2016 – It Just Runs Faster Announcement

SQL Server According to Bob

My development collogues and I are starting a regular blog series, outlining the vast range of scalability improvements, allowing SQL Server 2016 to run across a wide array of hardware configurations, faster and better than previous releases of SQL Server. The following table is taken from an ASP.NET, session state cache, stress test.

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

Is Intel Doomed in the Server CPU Space?

SQL Performance

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. This made it easier for database professionals to make the case for a hardware upgrade, and made the typical upgrade more worthwhile.

Servers 46
article thumbnail

The Performance Inequality Gap, 2021

Alex Russell

A then-representative $200USD device had 4-8 slow (in-order, low-cache) cores, ~2GiB of RAM, and relatively slow MLC NAND flash storage. Hardware Past As Performance Prologue. Regardless, the overall story for hardware progress remains grim, particularly when we recall how long device replacement cycles are: Tap for a larger version.

article thumbnail

Front-End Performance Checklist 2020 [PDF, Apple Pages, MS Word]

Smashing Magazine

On the other hand, we have hardware constraints on memory and CPU due to JavaScript parsing times (we’ll talk about them in detail later). In real-life world, most products aren’t even close: an median bundle size today is around 417KB , which is up 42% compared to early 2015.

article thumbnail

Front-End Performance Checklist 2019 [PDF, Apple Pages, MS Word]

Smashing Magazine

On the other hand, we have hardware constraints on memory and CPU due to JavaScript parsing times (we’ll talk about them in detail later). In real-life world, most products aren’t even close: an average bundle size today is around 400KB , which is up 35% compared to late 2015. We could also go beyond the bundle size budget though.