SR/IOV, TB/USB4, PCIE NUC DEV KITS, ??? others???
In , a single system image (SSI) cluster is a  of machines that appears to be one single system,
I'm sure these thoughts have been previously "thunk", are "consumer" level nodes possible/ feasible for daily computing/ gaming  (with AND without consideration of "plug and play" or "It just works" or user friendly Graphical user interface environments 
 

hey sort of the opposite, in that scenario there is one physical machines cut up into a bunch of synthetic little ones 
 
what I'm interested in is multiple physicals "machines" shared "locally" (in the same location) communicating amongst or within one another running one instance of an OS "~seamlessly~" across/amongst this one "node/computer"
 
P.s i hope your human and not a bot promoting LTT

in , a single system image (SSI) cluster is a  cluster(group) of machines that appears to be one single system
 
Some SSI systems allow processes on different nodes to communicate using  mechanisms as if they were running on the same machine
 
trust me this isn't a ltt kind of topic, any resource for  Computing dictionary's, acronyms of computing? the medical dictionary for doctorates of PCs    and idk where to find "Whetzel" (sorry for the botched name)

(I'm familiar with) Threadripper, did you suggest it as you knew it could support Sli or because the of the number of pcie lanes over consumer options also be leveraged? 
I'm currently running on a Asus WS Z390 Pro thunderbolt add in ready and a broadcom chip
The ExpressLane™ PEX 8747 is a 48-lane, 5-port, PCIe Gen 3 switch device developed on 40nm technology. The PEX 8747 device offers Multi-Host PCI Express switching capability enabling users to connect a host to its respective endpoints via scalable, high bandwidth,
non-blocking interconnection to a variety of graphics applications. The PEX 8747 is optimized to support high-resolution graphics while supporting peer-to-peer traffic and multicast for maximum performance. Included is PLX's proprietary visionPAK, 
MOBO block diagram   
 
brodcom 8747 info    
 
 
with intel not viable until lga 1700 matures(or later) and AMD mainstream being some, but not justifiable improvement in performance(yet~), and Thredrippers all day attainable OC mhz frequencys/ipc likley are not amazing and might hinder performance on a "(drempt)gaming node)
 
 
i guess url's are BANNED if not addvertising evgas products,,, and after some time trying tto convert and compress things i could get 1/5 thing to upload so i did none,,, and included (vanishing)urls ://=P
ill try block again
 
 

dang.. i thought i sorted this out after the first guy, multiple physical compute units appearing as one just one selfish gamer gz
 
 

Working together as an operating system

The architecture and design of a distributed operating system must realize both individual node and global system goals. Architecture and design must be approached in a manner consistent with separating policy and mechanism. In doing so, a distributed operating system attempts to provide an efficient and reliable distributed computing framework allowing for an absolute minimal user awareness of the underlying command and control efforts.
The multi-level collaboration between a kernel and the system management components, and in turn between the distinct nodes in a distributed operating system is the functional challenge of the distributed operating system. This is the point in the system that must maintain a perfect harmony of purpose, and simultaneously maintain a complete disconnect of intent from implementation. This challenge is the distributed operating system's opportunity to produce the foundation and framework for a reliable, efficient, available, robust, extensible, and scalable system. However, this opportunity comes at a very high cost in complexity.

The price of complexity

In a distributed operating system, the exceptional degree of inherent complexity could easily render the entire system an anathema to any user. As such, the logical price of realizing a distributed operation system must be calculated in terms of overcoming vast amounts of complexity in many areas, and on many levels. This calculation includes the depth, breadth, and range of design investment and architectural planning required in achieving even the most modest implementation.
These design and development considerations are critical and unforgiving. For instance, a deep understanding of a distributed operating system's overall architectural and design detail is required at an exceptionally early point. An exhausting array of design considerations are inherent in the development of a distributed operating system. Each of these design considerations can potentially affect many of the others to a significant degree. This leads to a massive effort in balanced approach, in terms of the individual design considerations, and many of their permutations. As an aid in this effort, most rely on documented experience and research in distributed computing power.
 
CREDIT TO .  wikipidia  DOT ORG/wiki/Distributed_operating_system