Re: Chromium start-up time
Brian Paul <[email protected]>
| Newsgroups | gmane.comp.graphics.chromium.devel |
|---|---|
| Message-ID | <[email protected]> |
[email protected] wrote: > Hi, > > We currently have a 20 node display that we use with Chromium. All 20 nodes, including the Mothership and CRAppfaker run on Windows through Cygwin. > > I won't go into excruciating detail about our configuration except to say that we use one TileSort spu and 20 render spu's, that are added and configured through their appropriate nodes. > > The problem we noticed is that the start-up time to initialize all 20 displays, plus the CRAppfaker with the Mothership was extremely slow, taking more than 3 minutes execution time. > > I traced at least part of the problem down to the Mothership.py file and the __qualifyHostname__ function. It was spending 4.5 seconds to sit on the call to socket.getfqdn(host). We did not have DNS set up so I believe it was sitting on this call to fully qualify the host name and timing out after 4-4.5 seconds. Also, this function was being called twice per display node via the do_acceptrequest and do_connectrequest functions. Therefore, this was adding alot of time to wait for all of the displays to initialize. Could you please explain why it needs to fully qualify the name?? I'm not sure I understand why it needs to do this since if we just return immediately with the hostname that is passed in, it works just fine. > > Thanks, > Alicia It looks like that code was a patch from Joel Welling that I checked in last December. Maybe Joel can provide some info. -Brian ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click