Doing calculations for a lot of packets is very demanding on a server, and can one to its knees with ease.
Until we get a more efficient EU system, I propose the introduction of a Network Segmenter.
Here's how it would work:
The segmenter only allows EU to pass in one direction.
When placed on a wire, the segmenter determines which side is the "source" and which is the "sink" by looking for machines that take EU. The "source" side is whichever one has zero machines that consume EU.
Once the "source" side has been determined, the Segmenter finds the shortest route to every machine on the "source" side and determines the per-packet loss for each. It then stores a list of all the machines and the loss from each.
From then on the segmenter retrieves the power generated by each machine directly, deducts wire losses, and outputs the power it onto the "sink" network segment directly using the largest packet size the "sink" segment can tolerate. This skips all further network calculations for the "source" segment and minimizes the number of packets.
If the "sink" segment is a directly connected device then the power is added directly without the use of packets.
Such a machine would allow, for example, a field of 512 solar panels connected to an MFSU to involve zero packets, and thus a negligible server load.
A hypothetical "version two" would involve the segmenter mimicking the power production aspect of all "source" machines and simply deactivating the originals.
The segmenter would not function without a source network, nor would it function with a source network containing a nuclear reactor. In both cases it would block the transfer of EU between segments.