what is the role of workers with locally_exlusive_torch or locally_exclusive_cl?
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- python, pytorch
- 领域
- performance
调研方向
No files, tests, or entry points are named. Start by tracing how workers are handled by locally_exclusive and locally_exclusive_torch, then compare their CPU and GPU execution paths; document what workers mean for each mode, whether changing the count matters, and how the observed performance should be interpreted.
由索引模型根据 Issue 内容生成。
描述
I'm getting back in to motion correction, and I am testing out some new options.
I ran a test on 10 minutes of NPX 1.0 data. I used the locally_exclusive peak detection and completed the run in 212 seconds (timed using python's perf_counter) with 12 workers using a 28-logical processors ~3.7 GHz CPU (2024 i7). I then tested locally_exclusive_torch and completed the run in 216 seconds using the same settings on a 4000 Ada GPU. My task manager shows essentially 100% utilization of either CPU or GPU during these runs.
I noticed on the progress bar that the torch version also said it was using 12 workers.
What is the meaning of workers when we run something on the GPU? My understanding is that this is not typical language for the parallel processing on the GPU, and that typically we just let cuda run its magic "beneath the hood"
Would you recommend changing the number of workers when running these steps on GPU? Or does that not have a meaningful impact? If a process is parallelizable I would expect more of a performance improvement moving from CPU to GPU. Do you have any ideas if the performance I observed is expected?
- 主要语言
- Python
- 星标
- 847
- 派生
- 280
- 平均合并
- 3 天 9 小时
- 30 天内合并 PR
- 29
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
SpikeInterface/spikeinterface 的其他 Issue
-
testing
难度 2/5 1-3 小时 新手友好度 68/100
SpikeInterface/spikeinterface#4756 ·
-
难度 2/5 1-3 小时 新手友好度 74/100
SpikeInterface/spikeinterface#4745 ·
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
SpikeInterface/spikeinterface#4510 · 2 条评论 ·
-
performance
难度 4/5 3-5 天 新手友好度 55/100
SpikeInterface/spikeinterface#4787 ·
-
难度 4/5 3-5 天 新手友好度 30/100
SpikeInterface/spikeinterface#4781 · 1 条评论 ·
查看 SpikeInterface/spikeinterface 的全部 Issue
相似的 Issue
-
area/auth bug comp/agent P3 platform/discord type/security
难度 2/5 1-3 小时 新手友好度 88/100
NousResearch/hermes-agent#117848 ·
-
难度 2/5 1-3 小时 新手友好度 74/100
bancolombia/sentinel#23 ·
-
test md 未关闭CI
难度 2/5 1-3 小时 新手友好度 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
难度 2/5 1-3 小时 新手友好度 74/100
langchain-ai/deepagents#6450 ·
-
bug client
难度 2/5 1-3 小时 新手友好度 88/100