search

magland / sortingview

Web app for viewing results of ephys spike sorting
Apache License 2.0
25 stars 8 forks source link

Precompute snippets RAM usage problem #151

Closed lfrank closed 3 years ago

lfrank commented 3 years ago

We are trying to visualize https://www.figurl.org/fig?channel=franklab2&figureObject=0f0a972033745670dd414dae77ffde853f049876&label=wilbur20210401_.nwb_wilbur20210401_day_29

Right now the sortingview process is > 500 GB of RAM, and climbing, and has been running for ~2 hours.

The recording extractor itself is ~233 GB, so it's not clear why that much RAM usage is required. Can that be reduced?

magland commented 3 years ago

Closing because we are discussing on slack and working toward a solution that does not require one massive file for snippets.