News for hackers. Stuff that matters.

A comment on Latency Numbers Every Programmer Should Know. Parent comment

Re:Latency Numbers Every Programmer Should Know by scurvy on Wednesday September 05, 2018 @12:38PM (#17919560)
Don't forget fiber splices for accidental cuts. Engineers have to try their best to match the existing refraction when splicing in the new patch. Tools help, but there's a lot of skill and craftsmanship there.
[ Parent | on HN ]
Re:Latency Numbers Every Programmer Should Know by e12e on Wednesday September 05, 2018 @02:15PM (#17920557)
But a splice should either work, or not work? It is literally welding two glass strands into one?
[ Parent | on HN ]
Re:Latency Numbers Every Programmer Should Know by Hikikomori on Wednesday September 05, 2018 @05:56PM (#17922239)
A splice may or may not work, or something in between. The splice might cause enough attenuation that you go over your optical budget (signal strength and receiver sensitivity) so no link comes up. But it might come up just barely and then you may have some bad frames as a result.
[ Parent | on HN ]