Listen to this Post
Introduction
Brave Browser has announced a significant performance upgrade by optimizing its adblock engine, reducing memory usage by 30MB and improving browsing speed—especially on older devices. This enhancement, currently available in Brave Nightly, leverages flatbuffers for efficient filter storage, showcasing the browser’s commitment to engineering excellence.
Learning Objectives
- Understand how Brave’s adblock optimization reduces memory consumption.
- Learn about flatbuffers and their role in browser performance.
- Explore ways to apply similar optimizations in other privacy-focused tools.
You Should Know
1. How Flatbuffers Improve Memory Efficiency
Flatbuffers are a serialization library that stores data in a compact binary format, reducing parsing overhead. Brave now uses them for network filter storage.
Example Command (Linux):
Check memory usage before/after enabling Brave’s adblock $ ps -eo pid,user,%mem,command --sort=-%mem | grep brave
Steps:
- Run the command above to monitor Brave’s memory consumption.
2. Compare results with/without adblock lists enabled.
3. Observe the ~30MB reduction due to flatbuffers.
2. Testing Brave Nightly for Performance Gains
Brave Nightly is the experimental build where these optimizations are first deployed.
Windows Command:
Download Brave Nightly winget install Brave.Brave.Nightly
Steps:
- Install Brave Nightly via Winget (Windows) or from the official site (Linux/macOS).
- Monitor performance using browser task managers (Shift+Esc in Brave).
3. Verify reduced memory footprint with multiple tabs.
3. Enforcing Adblock Lists for Maximum Efficiency
Brave supports custom filter lists (e.g., EasyList, uBlock filters).
Linux Command:
Check active filter lists (Brave config path) $ cat ~/.config/BraveSoftware/Brave-Browser/Default/Preferences | grep "adblock"
Steps:
1. Navigate to `brave://adblock` in the browser.
2. Enable additional lists (e.g., “EasyPrivacy”).
3. Verify memory impact via system monitoring tools.
4. Comparing Brave’s Adblock to uBlock Origin
Brave’s built-in adblocker now rivals extensions like uBlock Origin in efficiency.
Browser Console (Debugging):
// Check blocked requests in Brave DevTools
chrome.webRequest.onBeforeRequest.addListener(
console.log, {urls: ["<all_urls>"]}, ["blocking"]
);
Steps:
1. Open DevTools (Ctrl+Shift+I).
2. Paste the snippet to log blocked requests.
3. Compare with uBlock Origin’s logger (`ublock0.dashboard`).
5. Future-Proofing Browser Performance
Brave plans further optimizations—here’s how to stay ahead:
Windows PowerShell (Monitoring):
Track Brave’s memory over time Get-Process -Name "brave" | Format-Table -AutoSize
Steps:
1. Run periodically to track memory trends.
- Correlate with Brave’s update logs for new optimizations.
What Undercode Say
- Key Takeaway 1: Brave’s shift to flatbuffers sets a precedent for efficient adblocking without third-party extensions.
- Key Takeaway 2: The ~30MB memory reduction is critical for low-end devices, enhancing accessibility.
Analysis:
Brave’s engineering team demonstrates how open-source browsers can outperform competitors through low-level optimizations. This update not only benefits users but also pressures other browsers (e.g., Chrome, Firefox) to adopt similar efficiency measures. Future updates may extend these gains to other components, like tracker blocking and crypto-wallet features.
Prediction
By 2025, expect mainstream browsers to adopt flatbuffer-like serialization, reducing baseline memory usage by 20–40%. Privacy tools will increasingly rely on compiled, low-overhead filtering, making adblockers faster and more resource-efficient. Brave’s approach could become the industry standard.
IT/Security Reporter URL:
Reported By: Brave Software – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅
