Tootfinder

Opt-in global Mastodon full text search. Join the index!

@azonenberg@ioc.exchange
2025-12-29 18:42:10

There's still room to tune - shallow memory throughput is definitely suboptimal due to latency issues I need to chase - but with deep memory ngscopeclient ThunderScope is getting some pretty impressive performance.
2 channels @ 50M point memory depth (100M points per trigger) streaming at 7.5 WFM/s over LAN from across the building through a router. 40Gbase-SR4 from client to core switch and from core switch to router, then back to core switch, then 10Gbase-SR to the machine host…

Screenshot of ngscopeclient displaying 50M points of data from two channels as a time domain waveform, FFT, and waterfall updating at 7.5 Hz
Filter graph showing the subtract, FFT, and waterfall filters each completing in single digit milliseconds on the GPU
@azonenberg@ioc.exchange
2026-01-01 07:03:03

Starting to look at some performance improvements for various scopehal filters as I begin the push for v0.2.
The benchmark dataset is P/N legs of 100baseTX Ethernet sampled at 500 Msps with a ThunderScope.
At 50M point memory depth, each waveform is 100 MB in size (2 channels * 8 bits * 500 Msps) and covers 100ms of real time.
The filter graph currently takes just shy of a second to run, meaning we're at 10% of real time. I want to improve on this.

ngscopeclient displaying an 3-level eye pattern and waveform
ngscopeclient filter graph showing a differential pair being subtracted, followed by CDR and an eye pattern