<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data Transfer Rate on Swabian Instruments</title><link>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/</link><description>Recent content in Data Transfer Rate on Swabian Instruments</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 20 Aug 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/index.xml" rel="self" type="application/rss+xml"/><item><title>CPU Performance Impact on Transfer Rate</title><link>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/cpu-performance-impact-on-transfer-rate/</link><pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate><guid>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/cpu-performance-impact-on-transfer-rate/</guid><description>&lt;p>We conducted tests to determine the maximum transfer rate achievable with different CPUs using either &lt;em>Time Tagger Ultra&lt;/em> or &lt;em>Time Tagger X&lt;/em>.
The transfer rate for the &lt;em>Time Tagger 20&lt;/em> is limited by USB 2.0 and,
therefore, does not depend on CPU performance.&lt;/p>
&lt;p>These results are indicative only and may vary with system load (background processes), power mode (plugged in vs on battery),
thermal throttling, and OS/driver settings.
To reproduce the measurements, use the example scripts included with the installation (default path):&lt;/p></description></item><item><title>Effects of USB Hubs and Docking Stations on Transfer Rate</title><link>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/effects-of-usb-hubs-and-docking-stations-on-transfer-rate/</link><pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate><guid>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/effects-of-usb-hubs-and-docking-stations-on-transfer-rate/</guid><description>&lt;p>High-quality USB hubs and docking stations do not reduce the data transfer rate from Time Taggers to the PC.
We conducted tests using both a USB hub
(&lt;a href="https://www.mcd-elektronik.com/products/conline-control-systems/usb-hub-30-6-port-switchable-2-control-inputs.html">MCD Elektronik GmbH, model: USB 3.0 HUB 6 &lt;/a>)
and a docking station (&lt;a href="https://www.lenovo.com/us/en/p/accessories-and-software/docking/docking_thunderbolt-docks-(universal-cable-docks)/40b00135us" > Lenovo ThinkPad Tunderbolt 4 Docking Station &lt;/a>)
to connect the &lt;em>Time Tagger X&lt;/em> to a PC. In both cases, we found that the transfer rate was similar to that of the &lt;em>Time Tagger X&lt;/em> when it was directly connected to the computer.&lt;/p></description></item><item><title>Impact of Registered Channels on Transfer Rate</title><link>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/impact-of-registered-channels-on-transfer-rate/</link><pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate><guid>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/impact-of-registered-channels-on-transfer-rate/</guid><description>&lt;p>The number of registered channels does not affect the overall transfer rate of a Time Tagger.&lt;/p>
&lt;p>To demonstrate this, we enabled the test signals and aligned them in time. We measured the transfer rate for all Time Taggers models.
Until Software version v2.16, the transfer rate for &lt;em>Time Tagger Ultra&lt;/em> used to decrease by aligning more than 4 channels,
reaching a max transfer rate of 36 MTags/s with 18 channels aligned.&lt;/p></description></item><item><title>Low Count Rate Due to CPU Overload</title><link>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/low-count-rate-due-to-cpu-overload/</link><pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate><guid>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/low-count-rate-due-to-cpu-overload/</guid><description>&lt;p>A low countrate may occur due to CPU overload, especially during computationally intensive measurements.&lt;/p>
&lt;p>
Each initialized measurement runs on its own thread, but only a few of our API measurements,
such as &lt;a href="https://www.swabianinstruments.com/static/documentation/TimeTagger/api/Measurements.html#histogramlogbins">HistogramLogBins &lt;/a>,
can utilize multiple cores. If a single measurement consumes excessive CPU time, the Time Tagger's hardware buffer can fill up, leading to an overflow event and data loss.
&lt;/p>
&lt;h4>Example Scenario&lt;/h4>
&lt;p>
Consider a time-resolved imaging experiment with 500 pixels × 500 pixels × 1000 bins per histogram, resulting in approximately 1 GByte of data.
Modern high-performance computers (e.g., processors with DDR5 RAM) have a CPU-to-RAM bandwidth of about 38.4 GByte/s.
&lt;/p></description></item><item><title>Transfer Rate Limits for Each Time Tagger Model</title><link>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/transfer-rate-limits-for-each-time-tagger-model/</link><pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate><guid>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/transfer-rate-limits-for-each-time-tagger-model/</guid><description>&lt;p>&lt;em>Time Tagger Ultra&lt;/em> (TTU) and &lt;em>Time Tagger X&lt;/em> (TTX) utilize a USB 3 interface, allowing a maximum transfer rate of approximately &lt;strong> 90 MTags/s &lt;/strong>.
On the other hand, &lt;em>Time Tagger 20&lt;/em> (TT20) uses a USB 2 interface, which limits the maximum transfer rate to about &lt;strong> 9 MTags/s &lt;/strong>.
It is worth noting that the transfer rates depend on many different variables, e.g., CPU performance, workload from other running processes,
power and performance settings, etc.
The results mentioned above can only be achieved using a high-performance CPU with minimal workload from other applications running on the same computer.&lt;/p></description></item><item><title>Transfer Rate Using Time Tagger Network</title><link>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/transfer-rate-using-time-tagger-network/</link><pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate><guid>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/transfer-rate-using-time-tagger-network/</guid><description>&lt;p>The maximum transfer rate using Time Tagger Network is limited to the transmission speed of your local network.
A widely adopted transmission technology in modern network infrastructures is the Gigabit Ethernet (GbE) that enables data rate of 1 Gbps.
This limits the transfer rate from the &lt;em>Time Tagger Ultra&lt;/em> or &lt;em>Time Tagger X&lt;/em> to PC over the network up to 29 MTags/s.&lt;/p></description></item><item><title>USB Extenders and Their Impact on Transfer Rate</title><link>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/usb-extenders-and-their-impact-on-transfer-rate/</link><pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate><guid>https://www.swabianinstruments.com/knowledge/base/data-transfer-rate/usb-extenders-and-their-impact-on-transfer-rate/</guid><description>&lt;p>High-quality USB extenders and hubs do not reduce the data transfer rate from Time Taggers to the PC.&lt;/p>
&lt;p>We tested several USB extenders using a &lt;em>Time Tagger X&lt;/em> and &lt;em>Time Tagger Ultra&lt;/em>,
connected to a USB 3.0 port on a PC (CPU AMD Ryzen 9 5950X 16-Core 3.40GHz)
with only essential background processes running.
The maximum data transfer rates achieved aligned with the
&lt;a href="https://www.swabianinstruments.com/static/downloads/TimeTaggerSeries.pdf">Time Tagger Specifications &lt;/a>.&lt;/p>
&lt;br>
&lt;h5> Recommended USB 3.x Extenders (Copper): &lt;h5>
&lt;ul>
&lt;li>Lindy Active Extension Pro Series - available lengths: 8 / 10/ 15 / 20 / 30m &lt;br>E.g., 10m extender: &lt;a href="https://www.lindy.eu/10m-USB-3-0-Active-Extension-Pro.htm?websale8=ld0101.ld021102&amp;pi=43157">Lindy 43157&lt;/a>&lt;/li>
&lt;/ul>
&lt;br>
&lt;h5> Recommended USB 3.x Optical Extenders: &lt;h5>
&lt;p>For galvanically isolated extenders, we tested the following model:&lt;/p></description></item></channel></rss>