Remove 2007 Remove Latency Remove Virtualization
article thumbnail

A Decade of Dynamo: Powering the next wave of high-performance, internet-scale applications

All Things Distributed

The success of our early results with the Dynamo database encouraged us to write Amazon's Dynamo whitepaper and share it at the 2007 ACM Symposium on Operating Systems Principles (SOSP conference), so that others in the industry could benefit. This was the genesis of the Amazon Dynamo database.

Internet 120
article thumbnail

How To Measure the Working Set Size on Linux

Brendan Gregg

OSes usually show you virtual memory and resident memory, shown as the "VIRT" and "RES" columns in top. My tool does this using /proc/PID/clear_refs and the Referenced value from /proc/PID/smaps, which were added in 2007 by David Rientjes (thanks). That's the working set size. It is used for capacity planning and scalability analysis.

Cache 62
Insiders

Sign Up for our Newsletter

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

article thumbnail

How To Measure the Working Set Size on Linux

Brendan Gregg

OSes usually show you virtual memory and resident memory, shown as the "VIRT" and "RES" columns in top. My tool does this using /proc/PID/clear_refs and the Referenced value from /proc/PID/smaps, which were added in 2007 by David Rientjes (thanks). That's the working set size. It is used for capacity planning and scalability analysis.

Cache 40
article thumbnail

Progress Delayed Is Progress Denied

Alex Russell

Now in development in WebKit after years of radio silence, WebXR APIs provide Augmented Reality and Virtual Reality input and scene information to web applications. Since 2007, support for these features has barely improved. PWA Install Prompts. Offscreen Canvas. TextEncoderStream & TextDecoderStream.

Media 145
article thumbnail

Transforming enterprise integration with reactive streams

O'Reilly Software

WebServices, unfortunately, failed to deliver on the distributed systems front by having virtually all implementations using synchronous/blocking calls—which we all know is a recipe for scaling disaster. Schema evolution practices were rarely in place. Furthermore, the deployment tooling was not ready for SOA.