HiperSocket: Difference between revisions
PerfectBike (talk | contribs) mNo edit summary |
Restored revision 1050447458 by GhostInTheMachine (talk): Rv back to properly formatted article |
||
| (6 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{Short description|Software for communication within servers}} |
|||
{{Unreferenced|date=February 2012}} |
{{Unreferenced|date=February 2012}} |
||
'''HiperSockets''' is an [[IBM]] technology for high-speed communications between partitions on a server with a [[hypervisor]]. The term is most commonly associated with |
'''HiperSockets''' is an [[IBM]] technology for high-speed communications between partitions on a server with a [[hypervisor]]. The term is most commonly associated with [[System z9]] and later [[IBM Z]] mainframes which can provide in-memory [[TCP/IP]] connections between and among [[LPAR]]s running several different operating systems, including [[z/OS]], [[z/VM]], and [[Linux on IBM Z]]. |
||
Although applications perceive no functional differences, HiperSockets require less processing overhead on either side of the connections, improving performance. Since they are memory-based, they operate at memory speeds, reducing network latency and improving end-user performance, especially for complex applications which would otherwise require multiple network hops to fulfill requests. HiperSockets also provide security benefits, especially on the memory key-protected mainframe, even without encryption, because there is no opportunity to intercept a network connection. Moreover, HiperSockets improve reliability and availability because there are no network hubs, routers, adapters, or wires to break. |
Although applications perceive no functional differences, HiperSockets require less processing overhead on either side of the connections, improving performance. Since they are memory-based, they operate at memory speeds, reducing network latency and improving end-user performance, especially for complex applications which would otherwise require multiple network hops to fulfill requests. HiperSockets also provide security benefits, especially on the memory key-protected mainframe, even without encryption, because there is no opportunity to intercept a network connection. Moreover, HiperSockets improve reliability and availability because there are no network hubs, routers, adapters, or wires to break. |
||
| Line 10: | Line 11: | ||
==External links== |
==External links== |
||
*[ftp://public.dhe.ibm.com/common/ssi/pm/sp/n/zsd03016usen/ZSD03016USEN.PDF IBM eServer zSeries HiperSockets] |
*[ftp://public.dhe.ibm.com/common/ssi/pm/sp/n/zsd03016usen/ZSD03016USEN.PDF IBM eServer zSeries HiperSockets]{{dead link|date=November 2017 |bot=InternetArchiveBot |fix-attempted=yes }} |
||
*[http://www.redbooks.ibm.com/abstracts/sg246816.html HiperSockets Implementation Guide - IBM Redbooks] |
*[http://www.redbooks.ibm.com/abstracts/sg246816.html HiperSockets Implementation Guide - IBM Redbooks] |
||
Latest revision as of 21:48, 2 January 2025
 |
HiperSockets is an IBM technology for high-speed communications between partitions on a server with a hypervisor. The term is most commonly associated with System z9 and later IBM Z mainframes which can provide in-memory TCP/IP connections between and among LPARs running several different operating systems, including z/OS, z/VM, and Linux on IBM Z.
Although applications perceive no functional differences, HiperSockets require less processing overhead on either side of the connections, improving performance. Since they are memory-based, they operate at memory speeds, reducing network latency and improving end-user performance, especially for complex applications which would otherwise require multiple network hops to fulfill requests. HiperSockets also provide security benefits, especially on the memory key-protected mainframe, even without encryption, because there is no opportunity to intercept a network connection. Moreover, HiperSockets improve reliability and availability because there are no network hubs, routers, adapters, or wires to break.
The main disadvantage to HiperSockets is that they can only exist within a single physical system, so they are not applicable between and among physical systems. Server consolidation can help more applications use HiperSockets.