Re: Five Reasons Why Synchronous Networking Is Bad
Re: Five Reasons Why Synchronous Networking Is Bad
- Subject: Re: Five Reasons Why Synchronous Networking Is Bad
- From: Jens Alfke <email@hidden>
- Date: Thu, 5 Mar 2009 21:51:17 -0800
On Mar 5, 2009, at 7:39 PM, email@hidden wrote:
any browser I've ever used beachballs constantly as soon as I have
more than a handful of tabs open, and often even on a single tab.
Wow, that's very strange. I don't think that's at all typical. You did
upgrade your computer to more than 256MB of RAM, right? ;-)
It might be a filesystem call to load a picture or something
reading virtual memory, I don't really know. Contrast that with
Google's Chrome that from what I understand has a separate process
for each tab, or at least a process per server I believe. The
parent process should be able to manage the child processes without
ever beachballing.
Processes aren't a panacea, and they're more about security and crash-
resistance than about responsiveness; you could get the same
responsiveness benefit simply by making sure all the work for a tab
was done in a separate thread.
And the fact is that if the beachballing is due to VM thrash, that's
likely to affect all apps that are running, so process boundaries
don't help; breaking the browser into multiple process would actually
make things somewhat worse, because that's inevitably going to use
significantly more memory than a single process.
Anyway, I think we've established that this has nothing to do with
network APIs, so let's move on...
—Jens
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden