Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[2pt] graph-prototype: Investigate if we have unexpected runtime data processing regression/bottlenecks #124

Open
ivan-cukic opened this issue Jul 14, 2023 · 0 comments

Comments

@ivan-cukic
Copy link
Contributor

ivan-cukic commented Jul 14, 2023

graph-prototype has already surpassed its predecessor (GR 3.X) in terms of performance, thanks to the integration of lock-free buffers and optimized compile-time evaluated features. Nonetheless, we must be vigilant about avoiding unintentional performance regressions.

Our goal is to ensure graph-prototype is in top shape before it becomes GR 4.0 and expands its functionality. To do this, we need to conduct a comprehensive review to uncover any potential runtime data processing bottlenecks that might have slipped in.

Feedback from contributors such as @ivan-cukic , @mattkretz , and any other performance enthusiasts would be greatly appreciated. This performance review should ideally be completed before migrating graph-prototype to the GR repo.

@RalphSteinhagen RalphSteinhagen changed the title graph-prototype: Investigate if we have unexpected runtime data processing bottlenecks [] graph-prototype: Investigate if we have unexpected runtime data processing regression/bottlenecks Jul 15, 2023
@RalphSteinhagen RalphSteinhagen changed the title [] graph-prototype: Investigate if we have unexpected runtime data processing regression/bottlenecks [2pt] graph-prototype: Investigate if we have unexpected runtime data processing regression/bottlenecks Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants