<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Connection overhead</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/20918/connection-overhead</link><description>devzone.nordicsemi.com/.../ 
 In this blog this is written: 
 &amp;quot;Opening and closing a connection event adds a lot of overhead&amp;quot; 
 how much is the overhead and where can i look this up?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 30 Mar 2017 12:48:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/20918/connection-overhead" /><item><title>RE: Connection overhead</title><link>https://devzone.nordicsemi.com/thread/81696?ContentTypeID=1</link><pubDate>Thu, 30 Mar 2017 12:48:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b4ed7744-2ae8-4b06-9038-6d4d26781127</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;This is documented in the SDS document for the SoftDevice in question.&lt;/p&gt;
&lt;p&gt;For the S132 it can be found &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.sds/dita/softdevices/s130/ble_processor_avail_interrupt_latency/ble_peripheral_connection_performance.html?cp=2_3_0_0_15_2_2_1"&gt;here&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As you can see the worst case scenario is 55us of processing before the connection event, and 250us after.&lt;/p&gt;
&lt;p&gt;On top of that there might also be some additional overhead at the end of the connection event when using data length extension, if there is insufficient time at the end of the connection event to send another two packets at the maximum length.&lt;br /&gt;
As an example a full TX/RX sequence with 255 byte MTU at normal on air bitrate (1Mbps) will take more than 4ms, which means you can get a gap of up to 4ms at the end of the connection event if 255 byte MTU is enabled.&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;
Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>