Recently I've been reading about jumbo frames and I got confused in a few places. As far as I understand there is a lower bound on the Ethernet frame size between 'store and forward' points (layer 2 bridges) as frames need to be still being transmitted while it reaches the destination to enable collision detection. This limit is untouched by the jumbo frame setting.
Jumbo frames increase the upper bound of frame sizes from 1500B + headers to larger values (for example 4000B or 9000B + headers).
Larger frames allows lower overhead, etc., but there is more chance that single packet will be corrupted in transit beyond error correction capabilities. If a packet is corrupted it needs to be retransmitted (whole) adding to latency. Also the transmission of the packet takes more time as it needs to be (I believe) received fully before transferring to CPU or forwarding. However latency sensitive applications usually use UDP and custom packet sizes so they would not use jumbo frames (as long as they don't do MTU discovery) so they should not be affected by Jumbo Frames as the frames would be just shorter.
Given that I read jumbo frames hurt latency to a measurable degree I started wondering what is causing this effect?