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

Benchmarks - pmatch, pcons, and other core internal(possibly) #743

Open
SeungheonOh opened this issue Nov 12, 2024 · 0 comments
Open

Benchmarks - pmatch, pcons, and other core internal(possibly) #743

SeungheonOh opened this issue Nov 12, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request optimisation

Comments

@SeungheonOh
Copy link
Collaborator

pcons and pmatch are sude very frequently, hence changes in their performance can affect overall performance significantly. Benchmark with through cases for each of their usecases is need to ensure performance degradation my mistake.

Need to check: pmatch and pcons for each of encodings, both SOP types(Structs) and NP types(Records). Each types needs to check cases when some fields were used or not, and if each fields were used single time or multiple times.

@SeungheonOh SeungheonOh added enhancement New feature or request optimisation labels Nov 12, 2024
@SeungheonOh SeungheonOh changed the title Benchmarks - pmatch and pcons Benchmarks - pmatch, pcons, and other core internal(possibly) Nov 12, 2024
@t4ccer t4ccer self-assigned this Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request optimisation
Projects
None yet
Development

No branches or pull requests

2 participants