“Site Isolation does cause Chrome to create more renderer processes, which comes with performance tradeoffs,” admits Google software engineer Charlie Reis. “There is about a 10-13 percent total memory overhead in real workloads due to the larger number of processes.”