Testing suite is too slow
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 重构
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- python
- 领域
- performance, testing
调研方向
Start by reviewing the slow tests named in pytests/test_wavedecomposition.py and pytests/test_seismicinterpolation.py, then run the test suite with duration reporting to confirm the timings. The issue suggests reducing example dimensions; done means the suite runs faster without losing meaningful test coverage or causing CI failures.
由索引模型根据 Issue 内容生成。
描述
On a Intel Core i7-8565U CPU @ 1.80GHz × 8, the full test suite takes on average, 250s. I have noticed that tests are routinely failing in the GitHub CI, and I believe it may be because of this.
To profile the matter, I generated a list of all tests which take more than 2 seconds to run (see below). It seems WavefieldDecomposition and SeismicInterpolation are the biggest culprits, so one suggestions would be to make the dimensions in those examples smaller.
============================== slowest durations ===============================
26.72s call pytests/test_wavedecomposition.py::test_WavefieldDecomposition3D[par1]
25.61s call pytests/test_seismicinterpolation.py::test_SeismicInterpolation2d[par3]
17.35s call pytests/test_seismicinterpolation.py::test_SeismicInterpolation3d[par1]
8.76s call pytests/test_wavedecomposition.py::test_WavefieldDecomposition3D[par0]
8.37s call pytests/test_marchenko.py::test_Marchenko_timemulti_ana[par0]
6.01s call pytests/test_seismicinterpolation.py::test_SeismicInterpolation2d[par2]
5.30s call pytests/test_marchenko.py::test_Marchenko_freq[par0]
5.06s call pytests/test_marchenko.py::test_Marchenko_time_ana[par0]
5.02s call pytests/test_marchenko.py::test_Marchenko_time[par0]
5.01s call pytests/test_marchenko.py::test_Marchenko_freq[par1]
4.88s setup pytests/test_wavedecomposition.py::test_WavefieldDecomposition3D[par0]
4.88s call pytests/test_sparsity.py::test_ISTA_FISTA_multiplerhs[par3]
4.87s call pytests/test_sparsity.py::test_ISTA_FISTA_multiplerhs[par1]
4.74s call pytests/test_sparsity.py::test_ISTA_FISTA_multiplerhs[par5]
4.71s call pytests/test_sparsity.py::test_ISTA_FISTA_multiplerhs[par2]
4.64s call pytests/test_sparsity.py::test_ISTA_FISTA_multiplerhs[par0]
4.62s call pytests/test_sparsity.py::test_ISTA_FISTA_multiplerhs[par4]
4.16s call pytests/test_radon.py::test_Radon3D[par2]
3.41s call pytests/test_radon.py::test_Radon3D[par5]
3.36s call pytests/test_radon.py::test_Radon2D[par2]
3.34s call pytests/test_radon.py::test_Radon3D[par7]
3.17s call pytests/test_sparsity.py::test_ISTA_FISTA[par2]
3.11s call pytests/test_sparsity.py::test_ISTA_FISTA[par0]
3.10s call pytests/test_sparsity.py::test_ISTA_FISTA[par1]
3.07s call pytests/test_sparsity.py::test_ISTA_FISTA[par5]
2.99s call pytests/test_sparsity.py::test_ISTA_FISTA[par4]
2.96s call pytests/test_sparsity.py::test_ISTA_FISTA[par3]
2.69s call pytests/test_radon.py::test_Radon2D[par5]
2.30s call pytests/test_radon.py::test_Radon3D[par3]
2.21s call pytests/test_radon.py::test_Radon2D[par7]
- 主要语言
- Python
- 星标
- 539
- 派生
- 126
- 平均合并
- 2 天 17 小时
- 30 天内合并 PR
- 21
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
PyLops/pylops 的其他 Issue
-
Lipschitz method可能已有人在做 @Megumi1773 于 25 天前认领。 未关闭enhancement good first issue
难度 4/5 3-5 天 新手友好度 25/100
维护者通常 2 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 45/100
维护者通常 2 天内回复
-
CI
难度 3/5 1-2 天 新手友好度 52/100
维护者通常 2 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 25/100
维护者通常 2 天内回复
-
难度 3/5 1-2 天 新手友好度 38/100
PyLops/pylops#731 · 4 条评论 · 1 个 reaction ·
维护者通常 2 天内回复
相似的 Issue
-
cost:cheap practicality:seen-in-the-wild severity:medium
难度 2/5 1-3 小时 新手友好度 72/100
fairagro/m4.2_advanced_middleware_api#620 ·
维护者通常 1 天内回复
-
area:security effort:S priority:P2 provider:local-libvirt status:ready type:docs
难度 2/5 1-3 小时 新手友好度 75/100
randomparity/kdive#3495 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
microsoft/markitdown#2820 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复