article thumbnail

The Three Cs: Concatenate, Compress, Cache

CSS Wizardry

Compressing them over the network: Which compression algorithm, if any, will we use? Plotted on the same horizontal axis of 1.6s, the waterfalls speak for themselves: 201ms of cumulative latency; 109ms of cumulative download. 4,362ms of cumulative latency; 240ms of cumulative download. Read the complete test methodology.

Cache 291
article thumbnail

MongoDB Rollback: How to Minimize Data Loss

Scalegrid

Key Takeaways Rollbacks in MongoDB are triggered by disruptions in the replication process due to primary node crashes, network partitions, or other failures, which can lead to substantial data loss and inconsistencies. This failure in replication could happen due to crashes, network partitions, or other situations where failover occurs.

Database 130
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

Compression Methods in MongoDB: Snappy vs. Zstd

Percona

In this blog, we will discuss both data and network-level compression offered in MongoDB. We will discuss snappy and zstd for data block and zstd compression in a network. By default, MongoDB provides a snappy block compression method for storage and network communication. I am using PSMDB 6.0.4

Storage 105
article thumbnail

Mastering MongoDB® Timeout Settings

Scalegrid

MongoDB drivers provide several options for Mongo clients to handle different network timeout errors that may occur during usage. The default time-outs can significantly influence the behavior of your application when there are network errors.

Java 130
article thumbnail

Towards a Unified Theory of Web Performance

Alex Russell

The chief effect of the architectural difference is to shift the distribution of latency within the loop. Successive HTML documents tend to be highly repetitive , after all, with headers, footers, and shared elements continually re-created from source when navigating between pages. Today's web architecture debates (e.g.

article thumbnail

Seamlessly Swapping the API backend of the Netflix Android app

The Netflix TechBlog

For each route we migrated, we wanted to make sure we were not introducing any regressions: either in the form of missing (or worse, wrong) data, or by increasing the latency of each endpoint. You can find a lot more details about how this works in the Spinnaker canaries documentation. This meant that data that was static (e.g.

Latency 233
article thumbnail

The Performance Inequality Gap, 2023

Alex Russell

TL;DR : To serve users at the 75 th percentile ( P75 ) of devices and networks, we can now afford ~150KiB of HTML/CSS/fonts and ~300-350KiB of JavaScript (gzipped). This is a slight improvement on last year's budgets , thanks to device and network improvements. Networks #. This is an ethical crisis for the frontend.