• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

ATI Catalyst 4.10 Released!

Page 4 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: Megatomic
IMO, if the client and the server both run on the same machine neither one should need to go through the firewall to talk to the other.

(this is how it was explained to me, hope it makes sense 🙂)

"To allow interprocess communcations to work each task can send information using a network socket. This is usually just a layer 2 RAW socket and the port number is all that each task needs to know to share infromation. No data is sent over the wire and if you look at the firewall log you will see the source and dest are both localhost.

Socket layer communcations is about the same if not faster than shared memory since the memory has to be translated from one virtual space to another for the task to stay in sync. Semaphores are costly and not required with using open sockets. Linux uses localhost socket layer for interprocess comuncations a great deal."

 
Makes sense to me, thanks for the technical explanation. :beer:

Do you happen to have any insight into Sims 2 performance? 🙂
 
Back
Top