Remove 2018 Remove Architecture Remove Benchmarking Remove Website
article thumbnail

Top500 list: a brief introduction

PDC

It ranks the world’s 500 most powerful supercomputers based on their performance as measured by the Linpack benchmark. This is vividly reflected in the design on the Titan supercomputer , which is still among the world’s top 10 most powerful supercomputers (as of the November 2018 Top500 list). The Top500 list (Nov 2018).

Energy 40
article thumbnail

A look behind the scenes of AWS Lambda and our new Lambda monitoring extension

Dynatrace

At AWS re:Invent in 2018, the Lambda team presented an excellent talk. What the Lambda team introduced in 2018, for example, the new Firecracker VM, has since been fully rolled out. Depending on how resilient the calling system is, a failure in a Lambda function can potentially take down an entire website or application.

Lambda 218
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

KPTI/KAISER Meltdown Initial Performance Regressions

Brendan Gregg

I then analyzed performance during the benchmark ([active benchmarking]), and used other benchmarks to confirm findings. virtual (bgregg-c5.9xl-i-xxx) 02/09/2018 _x86_64_ (36 CPU) 05:24:51 PM proc/s cswch/s. See my previous post on [working set size estimation] and the full [website]. In more detail: ## 1.

article thumbnail

HammerDB MySQL and MariaDB Best Practice for Performance and Scalability

HammerDB

For anyone benchmarking MySQL with HammerDB it is important to understand the differences from sysbench workloads as HammerDB is targeted at a testing a different usage model from sysbench. As is also the case this limitation is at the database level (especially the storage engine) rather than the hardware level. c_ytd_payment: 10.00

article thumbnail

KPTI/KAISER Meltdown Initial Performance Regressions

Brendan Gregg

I then analyzed performance during the benchmark ([active benchmarking]), and used other benchmarks to confirm findings. virtual (bgregg-c5.9xl-i-xxx) 02/09/2018 _x86_64_ (36 CPU) 05:24:51 PM proc/s cswch/s. See my previous post on [working set size estimation] and the full [website]. In more detail: ## 1.

article thumbnail

The Performance Inequality Gap, 2024

Alex Russell

JavaScript-Heavy # Since at least 2015, building JavaScript-first websites has been a predictably terrible idea, yet most of the sites I trace on a daily basis remain mired in script. [1] Since 2010, volumes have been on a slow downward glide path , shrinking from ~350MM per year in a decade ago to ~260MM in 2018.

article thumbnail

The Performance Inequality Gap, 2021

Alex Russell

The risks embedded in these deep-wetware effects, and their cross-origin implications, mean that your website's success is partially a function of the health of the commons. India became a 4G-centric market sometime in 2018. If there's a bright spot in our construction of a 2021 baseline for performance, this is it.