Negative. Mileage varies from device to device, not to mention based on what a person’s settings may be. But I could go ahead and give you an AI answer:
The expected difference in RAM usage between opening a new tab and a new window in Brave is small but measurable. Here’s an estimate based on typical browser behavior:
- New Tab:
- Typically adds around 2-5 MB of RAM, depending on browser optimizations and extensions.
- Tabs share the same process within a window, so resources like the UI and core browser services are reused.
- New Window:
- May use 20-30 MB or more for the new process. This includes resources for the window frame, additional browser UI, and separate process isolation in some cases.
The actual numbers vary depending on:
- The operating system (e.g., Windows, macOS, Linux).
- Extensions installed (which can attach themselves to each tab or window).
- Browser settings (e.g., process isolation for security).
For an “empty” instance with no content loaded, the difference should be around 15-25 MB, with new windows using more RAM due to the extra overhead of a separate browser process.
But as 289wk mentioned, might just be beneficial for you to test on your own device to see what you notice.
AI Answer to your last reply:
There isn’t a fixed default value for memory consumption for a new tab or window because usage depends on dynamic factors like system resources, browser optimizations, and extensions. However, the baseline difference between a new tab (~2–5 MB) and a new window (~20–30 MB) is consistent for most systems.
Regarding swaps and cache:
- Swaps (virtual memory): Usually kick in only when physical RAM is under pressure, so they wouldn’t affect memory usage in normal scenarios for just opening tabs or windows.
- Cache: This can vary based on browser settings, the system’s available memory, and whether content (like cached assets) is reused between tabs/windows.
In repeated experiments, results might differ slightly because:
- Cached data can vary depending on what’s already in memory.
- System optimizations or resource contention may introduce small variations.
If you’re looking for a more consistent comparison, testing in a fresh session (with cache cleared) could give a closer approximation of the “default” RAM usage for tabs vs. windows.