Skip to content

Optimize SpikeRetriever and RAM usage for extensions - #4809

Open
alejoe91 wants to merge 7 commits into
SpikeInterface:mainfrom
alejoe91:optimize-retrievers
Open

alejoe91 wants to merge 7 commits into
SpikeInterface:mainfrom
alejoe91:optimize-retrievers

Conversation

@alejoe91

@alejoe91 alejoe91 commented Sep 29, 2026 •

Copy link
Copy Markdown
Member

This PR reduces the RAM usage for computing spiek-vector extensions by:

  • Only allocating sample_index array in spike_vector init (materializes for zarr, keeps as memmap -- fast -- for binary backend)
  • Avoid segment slices in case of mono-segment
  • Reduce dtype for spike locations and amplitude scalings from float64 to float32 (more than enough)

In addition, it also adds missing kwargs to the PipelineNodes

Here are some benchmarks and projections:
image

@alejoe91 alejoe91 added core Changes to core module performance Performance issues/improvements chronic labels Sep 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chronic core Changes to core module performance Performance issues/improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant