Issue 3173: First call to winsock async connect is slow
http://code.google.com/p/chromium/issues/detail?id=3173
Comment #1 by [EMAIL PROTECTED]:
So a little more research, I think most of this is do to delayed
initialization
that's not just specific to connect(). For example, calling WSASocket()
will also
take 6ms the first time. This can be traced down to DPROVIDER__Initialize,
which
calls LoadLibraryA("mswsock.dll"). I think it might be an idea to try to
load some
of this earlier on and in parallel. DNS requests also need mswsock, so it
would need
to be earlier than that. It would be best to do it some time when we won't
be
fighting over the loader lock...
Issue attribute updates:
Cc: [EMAIL PROTECTED]
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" 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-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
