My statement is that the memory footprints shown are representative enough. The way the Chrome API works regarding the handling of net requests is that all extensions are executed to inspect each net request, even if one of them cancels that net request. So basically they have the same workload.