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

Performance regression #57

Open
anyuser opened this issue Sep 30, 2024 · 0 comments
Open

Performance regression #57

anyuser opened this issue Sep 30, 2024 · 0 comments

Comments

@anyuser
Copy link

anyuser commented Sep 30, 2024

I have been using an older version of this library for a while (here). It was a version from a few years ago where pooling was partly implemented, but it still generated repeated GC allocations in some places. There was a UsePooling setting, which is on in my project.

Now I tried updating the library to the last version here with "full" pooling support, and the performance is much worse. The same tesselation of a polygon blob for testing takes around 50x more time than with the old version. Most time seems to be spent in DefaultPool.Return().

Old:
Screenshot 2024-09-30 at 10 14 44

New:
Screenshot 2024-09-30 at 10 04 17

Note: This is profiled with Unity's "deep" profiling, so profiling itself distorts the numbers a bit. But it's also very noticeable without deep profiling.

Is this a known issue? Any Ideas what could be the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant