Keep in mind that pipes are not really the fastest IPC mechanism for windows. Mike had a much faster shared memory based solution. However, we found that the pipe based solution was easiest to integrate with the sandbox, and it was also fast enough such that other factors outweigh the performance differential between the two mechanisms. I guess what I'm saying is that we should probably not get too caught up in the performance differences here unless we think that is the dominant factor. Other things might be more important such as how easy it is to exchange shared memory and waitable events (the equivalent of a windows event object). -Darin
On Wed, Nov 12, 2008 at 7:07 PM, Jeremy Moskovich <[EMAIL PROTECTED]>wrote: > Hi Dan, > > Looking at the current IPC behavior is definitely on my list of things to > do. > > I don't think that should change the interpretation of the data though. > According to our measurements, Mach messages are always faster *. > > So the question becomes, not is it faster, but by how many orders of > magnitude. > > Best regards, > Jeremy > > * Using inline messages there's a break even at some point as the cost of > copying data takes over, but as discussed we can use OOL messages to get > really fast (~30uSec) constant time sends for messages >5K. > > On Wed, Nov 12, 2008 at 5:08 PM, Dan Kegel <[EMAIL PROTECTED]>wrote: > >> >> On Wed, Nov 12, 2008 at 4:46 PM, Jeremy Moskovich <[EMAIL PROTECTED]> >> wrote: >> > We ran some benchmarks of Mach ports vs FIFOs on OSX, you can find the >> > results in the "Performance Considerations" section of the Design doc. >> >> I don't see any measurements showing what typical Chrome >> IPC traffic looks like. Without that, it's hard to interpret >> your results. If I missed it, please point me to it. >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
