GSoC 2025 Proposal: Benchmarking & Performance for SymPy This project will:
- Move existing benchmarks to sympy_benchmarks. - Add missing benchmarks for key functions. - Automate ASV benchmarking via GitHub Actions. - Improve PR feedback for performance regressions. - Optimize slow-performing parts of SymPy. *Deliverables* - Consolidate benchmarks in sympy_benchmarks. - Automate benchmarking with ASV + GitHub Actions. - Improve benchmark reports in PRs. - Optimize at least one major slowdown in SymPy. *Timeline* - *Weeks 1-2:* Move benchmarks to sympy_benchmarks. - *Weeks 3-4:* Add missing benchmarks. - *Weeks 5-6:* Set up ASV automation. - *Weeks 7-8:* Improve GitHub Actions PR reports. - *Weeks 9-12:* Optimize performance & finalize work. Additionally, would it be good to move a small benchmark from the main SymPy repo to sympy_benchmarks? On Wednesday, March 5, 2025 at 3:02:15 AM UTC+5:30 [email protected] wrote: > If you want to you can, although it isn't required. > > Aaron Meurer > > On Mon, Mar 3, 2025 at 8:40 PM PRAYAG V <[email protected]> wrote: > > > > Before submitting the application to google.do I put my draft proposal > here.so you all can review and improve accordingly > > > > On Tuesday, February 18, 2025 at 12:28:39 AM UTC+5:30 [email protected] > wrote: > >> > >> On Mon, Feb 17, 2025 at 6:51 AM PRAYAG V <[email protected]> wrote: > >> > > >> > I’m interested in contributing to SymPy’s Benchmarking and > Performance project for GSoC. I’d like to help move benchmarks to the > sympy_benchmarks repo, add new ones, and set up continuous benchmarking. > Additionally, I’m excited to improve performance and the GitHub Actions bot. > >> > > >> > Do I need to draft a proposal and submit it to Google Groups within a > week? > >> > >> No. The GSoC program hasn't even started yet. We don't even find out > >> if Google has selected SymPy to be a mentoring organization until > >> later this week. The application period opens March 24 and the > >> deadline is April 8. See > >> https://developers.google.com/open-source/gsoc/timeline. > >> > >> However, you are definitely encouraged to work with us early, and past > >> experience has shown that this can be an advantage for applicants > >> because you will have more opportunity to learn about the SymPy > >> codebase and development practices, and develop your project proposal > >> ideas better. I would start by going through the performance and > >> benchmarking related issues in the sympy and sympy_benchmarks repos > >> and getting an idea of what needs to be done seeing where you can > >> start to contribute. > >> > >> Aaron Meurer > >> > >> > > >> > Thanks > >> > > >> > -- > >> > You received this message because you are subscribed to the Google > Groups "sympy" group. > >> > To unsubscribe from this group and stop receiving emails from it, > send an email to [email protected]. > >> > To view this discussion visit > https://groups.google.com/d/msgid/sympy/96780ba6-00d2-41a3-bec0-99c9af6bddaan%40googlegroups.com > . > > > > -- > > You received this message because you are subscribed to the Google > Groups "sympy" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > To view this discussion visit > https://groups.google.com/d/msgid/sympy/6ab37be7-b511-444d-8a6a-3d1fe1af076an%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sympy/25f7e3fb-5156-46bc-81cd-e6a4bf8d9c75n%40googlegroups.com.
