Ideas Test


Run protocol analyzers in background threads

I have captures of around 3GB, and I'm trying to analyze 3 separate SPI bit-streams in the capture. Unfortunately the UI freezes for extended periods of time while trying to decode all the data.

Instead of performing the protocol analysis on the UI thread; it would be far better to run the protocol analyzers in separate threads which would leave the UI responsive for navigation. Additionally this would result in faster execution when using multiple protocol analyzers on any modern processor with multiple cores.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 26 2018
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 18:27

    Hi Malcolm,

    This sounds like a bug. The analyzers themselves produce data on background threads, however the application may slow down if memory allocation starts to slow down.
    Most likely though this is actually a bug in the protocol search system. If you disable protocol search in the preferences, and then restart the software and try again, the performance might improve dramatically. Also, please open a support ticket and provide the following:
    Length of capture.
    Number of enabled channels (analog and digital)
    sample rate.
    SPI clock speed.
    estimation of SPI bus utilization (is it transferring data non-stop, or is it highly "bursty" with long idle times)
    This will help us setup a simulation and run a benchmark on it to figure out what's going wrong.