multiple process

what i have observed on google chrome was it was opening a new process on each tab or window. is http2 does the same thing? how about memory and processor consumption? i am concerned because it maybe affect the budget of webmasters.

That has nothing to do with HTTP protocol. Chrome creates separate processes for each tab, so each page request is not slowed down by requests done in other tabs.

Also, if one process crashes due to some unstable browser extension, it will not affect the processes in other tabs.

On the server side, nothing changes. If separate processes are created to handle different requests, like in Apache with pre-fork mode which most PHP sites use, it will continue to work that way.

As explained in the article, HTTP 2.0/SPDY only affects the transport layer, i.e. the way browsers and servers exchange request data.

Hello Manuel,

I'd like to just add that your statement about Google Chrome should be updated to

"Also, if one process crashes due to some unstable browser extension, it SHOULD not affect the processes in other tabs." :)

I am not sure what is the difference of meaning between what I said and what you corrected.

The difference is that 'will not' means there is not a way it could possibly ever effect other tabs. Changing it to 'should not' implies that while it shouldn't ever happen a possibility could exist that remains unknown that could cause one tab to interfere with another.

Right but each tab content is loaded and processed by a separate process. So I do not see how the possibility of different tabs affecting each other may exist.

Well, it doesn't happen often, but time to time my Chrome browser freezes completely or sometimes two tabs with pages of same domain stops working. That's why I used "should". It was supposed to be a tiny little joke, don't worry :).