Are you over 18 and want to see adult content?
More Annotations
A complete backup of www.shoepalace.com
Are you over 18 and want to see adult content?
A complete backup of www.www.relaxchile.cl
Are you over 18 and want to see adult content?
A complete backup of girlsgogames.com
Are you over 18 and want to see adult content?
A complete backup of www.aerisdies.com
Are you over 18 and want to see adult content?
A complete backup of www.azz-overload.net
Are you over 18 and want to see adult content?
A complete backup of femaledominationworld.com
Are you over 18 and want to see adult content?
A complete backup of www.www.hotgirlclub.com
Are you over 18 and want to see adult content?
A complete backup of www.www.amyellisnutt.com
Are you over 18 and want to see adult content?
A complete backup of www.www.thetabutales.com
Are you over 18 and want to see adult content?
A complete backup of www.argentinalove.net
Are you over 18 and want to see adult content?
Favourite Annotations
A complete backup of kumsaltarim.com.tr
Are you over 18 and want to see adult content?
A complete backup of onlinevirivky.cz
Are you over 18 and want to see adult content?
Text
MARC BROOKER'S BLOG
14 Dec 2013 Hardware Lock Elision on Haswell. 14 Jul 2013 Beyond iostat: Storage performance analysis with blktrace. 25 May 2013 Some Patterns of Engineering Design Meetings. 20 Jan 2013 Exploring TLA+ with two-phase commit. 06 Jan 2013 METASTABILITY AND DISTRIBUTED SYSTEMS Metastability and Distributed Systems. What if computer science had different parents? There's no more time-honored way to get things working again, from toasters to global-scale distributed systems, than turning them off and on again. READING RESEARCH: A GUIDE FOR SOFTWARE ENGINEERS Reading Research: A Guide for Software Engineers. Don't be afraid. One thing I'm known for at work is reading research papers, and referring to results in technical conversations. People ask me if, and how, they should read papers themselves. This post is a long-form answer to thatquestion.
WHY DO WE NEED DISTRIBUTED SYSTEMS? Distributed storage systems continuously make multiple copies of a piece of data, allowing a great deal of flexibility around cost, time-to-recovery, durability, and other factors. They can also be built to be extremely tolerant to correlated failures, and avoid correlation outright. TAIL LATENCY MIGHT MATTER MORE THAN YOU THINK Tail Latency Might Matter More Than You Think. A frustratingly qualitative approach. Tail latency, also known as high-percentile latency, refers to high latencies that clients see fairly infrequently. Things like: "my service mostly responds in around 10ms, but sometimes takes around 100ms". There are many causes of tail latency in the world INCIDENT RESPONSE ISN'T ENOUGH Incident Response Isn't Enough. Single points of failure become invisible. Postmortems, COEs, incident reports. Whatever your organization calls them, when done right they are a popular and effective way of formalizing the process of digging into system failures, and driving change. The success of this approach has lead some to believe that WHAT YOU CAN LEARN FROM OLD HARD DRIVE ADVERTS What You Can Learn From Old Hard Drive Adverts. The single most important trend in systems. Adverts for old computer hardware, especially hard drives, are a fun staple of computer forums and the nerdier side of the internet 1.For example, a couple SODIUM CARBONATE, AND RAMENIZED PASTA Sodium Carbonate, and Ramenized Pasta. Doing chemistry with baking soda, cabbage and an oven. Ramenizing things is super popular right now. The idea seems to have originated from the Ideas In Food crew, and is obviously adapted from the practice of making Ramen in Japan and similar alkaline noodles in China. In those recipes, the secret is incorporating an alkaline ingredient (such as kansui TWO TRAPS IN IOSTAT: %UTIL AND SVCTM Two traps in iostat: %util and svctm. These commonly-used fields in iostat shouldn't be commonly-used. iostat, from the excellent sysstat suite of utilities, is the go-to tool for evaluating IO performance on Linux. It's obvious why that's the case: sysstat is very useful, solid, and widely installed. CAP AND PACELC: THINKING MORE CLEARLY ABOUT CONSISTENCY CAP and PACELC: Thinking More Clearly About Consistency. CAP is confusing. PACELC is better, but still not ideal. In some sense, the CAP theorem has been too successful. With its snappy name and apparently easy-to-understand behavior, CAP has become the go-to way of talking about tradeoffs in distributed systems.MARC BROOKER'S BLOG
14 Dec 2013 Hardware Lock Elision on Haswell. 14 Jul 2013 Beyond iostat: Storage performance analysis with blktrace. 25 May 2013 Some Patterns of Engineering Design Meetings. 20 Jan 2013 Exploring TLA+ with two-phase commit. 06 Jan 2013 METASTABILITY AND DISTRIBUTED SYSTEMS Metastability and Distributed Systems. What if computer science had different parents? There's no more time-honored way to get things working again, from toasters to global-scale distributed systems, than turning them off and on again. READING RESEARCH: A GUIDE FOR SOFTWARE ENGINEERS Reading Research: A Guide for Software Engineers. Don't be afraid. One thing I'm known for at work is reading research papers, and referring to results in technical conversations. People ask me if, and how, they should read papers themselves. This post is a long-form answer to thatquestion.
WHY DO WE NEED DISTRIBUTED SYSTEMS? Distributed storage systems continuously make multiple copies of a piece of data, allowing a great deal of flexibility around cost, time-to-recovery, durability, and other factors. They can also be built to be extremely tolerant to correlated failures, and avoid correlation outright. TAIL LATENCY MIGHT MATTER MORE THAN YOU THINK Tail Latency Might Matter More Than You Think. A frustratingly qualitative approach. Tail latency, also known as high-percentile latency, refers to high latencies that clients see fairly infrequently. Things like: "my service mostly responds in around 10ms, but sometimes takes around 100ms". There are many causes of tail latency in the world INCIDENT RESPONSE ISN'T ENOUGH Incident Response Isn't Enough. Single points of failure become invisible. Postmortems, COEs, incident reports. Whatever your organization calls them, when done right they are a popular and effective way of formalizing the process of digging into system failures, and driving change. The success of this approach has lead some to believe that WHAT YOU CAN LEARN FROM OLD HARD DRIVE ADVERTS What You Can Learn From Old Hard Drive Adverts. The single most important trend in systems. Adverts for old computer hardware, especially hard drives, are a fun staple of computer forums and the nerdier side of the internet 1.For example, a couple SODIUM CARBONATE, AND RAMENIZED PASTA Sodium Carbonate, and Ramenized Pasta. Doing chemistry with baking soda, cabbage and an oven. Ramenizing things is super popular right now. The idea seems to have originated from the Ideas In Food crew, and is obviously adapted from the practice of making Ramen in Japan and similar alkaline noodles in China. In those recipes, the secret is incorporating an alkaline ingredient (such as kansui TWO TRAPS IN IOSTAT: %UTIL AND SVCTM Two traps in iostat: %util and svctm. These commonly-used fields in iostat shouldn't be commonly-used. iostat, from the excellent sysstat suite of utilities, is the go-to tool for evaluating IO performance on Linux. It's obvious why that's the case: sysstat is very useful, solid, and widely installed. CAP AND PACELC: THINKING MORE CLEARLY ABOUT CONSISTENCY CAP and PACELC: Thinking More Clearly About Consistency. CAP is confusing. PACELC is better, but still not ideal. In some sense, the CAP theorem has been too successful. With its snappy name and apparently easy-to-understand behavior, CAP has become the go-to way of talking about tradeoffs in distributed systems. READING RESEARCH: A GUIDE FOR SOFTWARE ENGINEERS Reading Research: A Guide for Software Engineers. Don't be afraid. One thing I'm known for at work is reading research papers, and referring to results in technical conversations. People ask me if, and how, they should read papers themselves. This post is a long-form answer to thatquestion.
THE FUNDAMENTAL MECHANISM OF SCALING The Fundamental Mechanism of Scaling. It's not Paxos, unfortunately. A common misconception among people picking up distributed systems is that replication and consensus protocols—Paxos, Raft, and friends—are the tools used to build the largest and most scalable systems. It's obviously true that these protocols are importantbuilding blocks.
TWO YEARS WITH RUST
Two Years With Rust. I like it. I hope it's going to be big. It's been just over two years since I started learning Rust. Since then, I've used it heavily at my day job, including work in the Firecracker code base, and a number of other projects. Rust is a great fit for the systems-level work I've been doing over the last few years: often performance- and density-sensitive, always security PHYSALIA: MILLIONS OF TINY DATABASES Physalia is a custom transactional key-value store, designed to play the role of configuration master in the EBS architecture. Last year, we wrote a paper about Physalia, and were thrilled that it was accepted to NSDI'20. Millions of Tiny Databases describes our problemand solution in
CODE ONLY SAYS WHAT IT DOES Code says what it does. That's important for the computer, because code is the way that we ask the computer to do something. It's OK for humans, as long as we never have to modify or debug the code. As soon as we do, we have a problem. Fundamentally, debugging is an exercise in changing what a program does to match what it should do. SODIUM CARBONATE, AND RAMENIZED PASTA Sodium Carbonate, and Ramenized Pasta. Doing chemistry with baking soda, cabbage and an oven. Ramenizing things is super popular right now. The idea seems to have originated from the Ideas In Food crew, and is obviously adapted from the practice of making Ramen in Japan and similar alkaline noodles in China. In those recipes, the secret is incorporating an alkaline ingredient (such as kansui THE OPERATIONS GRADIENT: IMPROVING SAFETY IN COMPLEX The Operations Gradient: Improving Safety in Complex Systems. Can we improve the safety of complex systems by listening to operators more? This week, I watched an excellent lecture by Richard Cook.He goes in some detail about why failures happen, through the lens of Rasmussen's model of system safety. BEYOND IOSTAT: STORAGE PERFORMANCE ANALYSIS WITH BLKTRACE Beyond iostat: Storage performance analysis with blktrace. An under appreciated set of IO analysis tools. If you've spent much time at all investigating IO performance on Linux, you're no doubt already familiar with iostat from the venerable sysstat package. iostat is the go-to tool for Linux storage performance monitoring with good reason: it's available nearly everywhere, it works on the THE POWER OF TWO RANDOM CHOICES The power of two random choices. Using less information to make better decisions. In many large-scale web services, multiple layers of stateless and stateful services are seperated by load balancers. Load balancing can be done with dedicated hardware, with dedicated software load balancers, using DNS trickery or through a load-balancing JITTER: MAKING THINGS BETTER WITH RANDOMNESS Jitter: Making Things Better With Randomness. Jitter is a good thing. Two weeks ago, I wrote an article titled Exponential Backoff and Jitter for the AWS Architecture blog. It looks at OCC in particular, but the lessons are applicable to all distributed systems.MARC BROOKER'S BLOG
14 Dec 2013 Hardware Lock Elision on Haswell. 14 Jul 2013 Beyond iostat: Storage performance analysis with blktrace. 25 May 2013 Some Patterns of Engineering Design Meetings. 20 Jan 2013 Exploring TLA+ with two-phase commit. 06 Jan 2013 METASTABILITY AND DISTRIBUTED SYSTEMS Metastability and Distributed Systems. What if computer science had different parents? There's no more time-honored way to get things working again, from toasters to global-scale distributed systems, than turning them off and on again. READING RESEARCH: A GUIDE FOR SOFTWARE ENGINEERS Reading Research: A Guide for Software Engineers. Don't be afraid. One thing I'm known for at work is reading research papers, and referring to results in technical conversations. People ask me if, and how, they should read papers themselves. This post is a long-form answer to thatquestion.
WHY DO WE NEED DISTRIBUTED SYSTEMS? Distributed storage systems continuously make multiple copies of a piece of data, allowing a great deal of flexibility around cost, time-to-recovery, durability, and other factors. They can also be built to be extremely tolerant to correlated failures, and avoid correlation outright. PHYSALIA: MILLIONS OF TINY DATABASES Physalia is a custom transactional key-value store, designed to play the role of configuration master in the EBS architecture. Last year, we wrote a paper about Physalia, and were thrilled that it was accepted to NSDI'20. Millions of Tiny Databases describes our problemand solution in
TAIL LATENCY MIGHT MATTER MORE THAN YOU THINK Tail Latency Might Matter More Than You Think. A frustratingly qualitative approach. Tail latency, also known as high-percentile latency, refers to high latencies that clients see fairly infrequently. Things like: "my service mostly responds in around 10ms, but sometimes takes around 100ms". There are many causes of tail latency in the world INCIDENT RESPONSE ISN'T ENOUGH Incident Response Isn't Enough. Single points of failure become invisible. Postmortems, COEs, incident reports. Whatever your organization calls them, when done right they are a popular and effective way of formalizing the process of digging into system failures, and driving change. The success of this approach has lead some to believe that CAP AND PACELC: THINKING MORE CLEARLY ABOUT CONSISTENCY CAP and PACELC: Thinking More Clearly About Consistency. CAP is confusing. PACELC is better, but still not ideal. In some sense, the CAP theorem has been too successful. With its snappy name and apparently easy-to-understand behavior, CAP has become the go-to way of talking about tradeoffs in distributed systems. TWO TRAPS IN IOSTAT: %UTIL AND SVCTM Two traps in iostat: %util and svctm. These commonly-used fields in iostat shouldn't be commonly-used. iostat, from the excellent sysstat suite of utilities, is the go-to tool for evaluating IO performance on Linux. It's obvious why that's the case: sysstat is very useful, solid, and widely installed. THE POWER OF TWO RANDOM CHOICES The power of two random choices. Using less information to make better decisions. In many large-scale web services, multiple layers of stateless and stateful services are seperated by load balancers. Load balancing can be done with dedicated hardware, with dedicated software load balancers, using DNS trickery or through a load-balancingMARC BROOKER'S BLOG
Blog Posts. 2021; 24 May 2021 Metastability and Distributed Systems; 19 Apr 2021 Tail Latency Might Matter More Than You Think; 14 Apr 2021 Redundant against what?; 25 Mar 2021 What You Can Learn From Old Hard Drive Adverts; 22 Feb 2021 Incident Response Isn't Enough; 22 Jan 2021 The Fundamental Mechanism of Scaling; 06 Jan 2021 Quorum Availability METASTABILITY AND DISTRIBUTED SYSTEMS Metastability and Distributed Systems. What if computer science had different parents? There's no more time-honored way to get things working again, from toasters to global-scale distributed systems, than turning them off and on again. READING RESEARCH: A GUIDE FOR SOFTWARE ENGINEERS Reading Research: A Guide for Software Engineers. Don't be afraid. One thing I'm known for at work is reading research papers, and referring to results in technical conversations. WHY DO WE NEED DISTRIBUTED SYSTEMS? Why do we need distributed systems? Building distributed systems is hard. It's expensive. It's complex. But we do it anyway. I grew up reading John Carmack's .plan file. PHYSALIA: MILLIONS OF TINY DATABASES Physalia: Millions of Tiny Databases. Avoiding Hard CAP Tradeoffs. A few years ago, when I was still working on EBS, we started building a system called Physalia. TAIL LATENCY MIGHT MATTER MORE THAN YOU THINK Tail Latency Might Matter More Than You Think. A frustratingly qualitative approach. Tail latency, also known as high-percentile latency, refers to high latencies that clients see fairly infrequently. Things like: "my service mostly responds in around 10ms, but sometimes takes around 100ms". INCIDENT RESPONSE ISN'T ENOUGH Incident Response Isn't Enough. Single points of failure become invisible. Postmortems, COEs, incident reports. Whatever your organization calls them, when done right they are a popular and effective way of formalizing the process of digging into system failures, and driving change. CAP AND PACELC: THINKING MORE CLEARLY ABOUT CONSISTENCY CAP and PACELC: Thinking More Clearly About Consistency. CAP is confusing. PACELC is better, but still not ideal. In some sense, the CAP theorem has been too successful. With its snappy name and apparently easy-to-understand behavior, CAP has become the go-to way of talking about tradeoffs in distributed systems. TWO TRAPS IN IOSTAT: %UTIL AND SVCTM Two traps in iostat: %util and svctm. These commonly-used fields in iostat shouldn't be commonly-used. iostat, from the excellent sysstat suite of utilities, is the go-to tool for evaluating IO performance on Linux. It's obvious why that's the case: sysstat is very useful, solid, and widely installed. THE POWER OF TWO RANDOM CHOICES The power of two random choices. Using less information to make better decisions. In many large-scale web services, multiple layers ofstateless and
READING RESEARCH: A GUIDE FOR SOFTWARE ENGINEERS Reading Research: A Guide for Software Engineers. Don't be afraid. One thing I'm known for at work is reading research papers, and referring to results in technical conversations. People ask me if, and how, they should read papers themselves. This post is a long-form answer to thatquestion.
TAIL LATENCY MIGHT MATTER MORE THAN YOU THINK Tail Latency Might Matter More Than You Think. A frustratingly qualitative approach. Tail latency, also known as high-percentile latency, refers to high latencies that clients see fairly infrequently. Things like: "my service mostly responds in around 10ms, but sometimes takes around 100ms". CODE ONLY SAYS WHAT IT DOES Code says what it does. That's important for the computer, because code is the way that we ask the computer to do something. It's OK for humans, as long as we never have to modify or debug the code. As soon as we do, we have a problem. Fundamentally, debugging is an exercise in changing what a program does to match what it should do.TWO YEARS WITH RUST
Two Years With Rust. I like it. I hope it's going to be big. It's been just over two years since I started learning Rust. Since then, I've used it heavily at my day job, including work in the Firecracker code base, and a number of other projects. Rust is a great fit for the systems-level work I've been doing over the last few years: often performance- and density-sensitive, always security CONSENSUS IS HARDER THAN IT LOOKS Consensus is Harder Than It Looks. And it looks pretty hard. In his classic paper How to Build a Highly Available System Using Consensus Butler Lampson laid out a pattern that's become very popular in the design of large-scale highly-available systems. Consensus is used to deal with unusual situations like host failures (Lampson says reserved for emergencies), and leases (time-limited locks WHAT YOU CAN LEARN FROM OLD HARD DRIVE ADVERTS What You Can Learn From Old Hard Drive Adverts. The single most important trend in systems. Adverts for old computer hardware, especially hard drives, are a fun staple of computer forums and the nerdier side of the internet 1.For example, a couple THE FUNDAMENTAL MECHANISM OF SCALING The Fundamental Mechanism of Scaling. It's not Paxos, unfortunately. A common misconception among people picking up distributed systems is that replication and consensus protocols—Paxos, Raft, and friends—are the tools used to build the largest and most scalable systems. It's obviously true that these protocols are importantbuilding blocks.
TELLING STORIES ABOUT LITTLE'S LAW Telling Stories About Little's Law. Building Up Intuition with Narrative. Little's Law is widely used as a tool for understanding the behavior of distributed systems. The law says that the mean concurrency in the system (𝐿) is equal to the mean rate at which requests arrive (λ) multiplied by the mean time that each request spends in the system (𝑊): IS THE MEAN REALLY USELESS? Don't be too mean to the mean. "The mean is useless" is a commonly-repeated statement in the systems observation and monitoring world. As people correctly point out, the mean (or average 1) tends to hide information about outliers, tends to be optimistic for many metrics, and can even be wildly misleading in presence of largeoutliers.
JITTER: MAKING THINGS BETTER WITH RANDOMNESS Jitter: Making Things Better With Randomness. Jitter is a good thing. Two weeks ago, I wrote an article titled Exponential Backoff and Jitter for the AWS Architecture blog. It looks at OCC in particular, but the lessons are applicable to all distributed systems.BROOKER.CO.ZA
There is currently no content here, except my blogDetails
Copyright © 2024 ArchiveBay.com. All rights reserved. Terms of Use | Privacy Policy | DMCA | 2021 | Feedback | Advertising | RSS 2.0