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

GC allocs for rendering #367

Open
lucasmontec opened this issue Aug 11, 2023 · 1 comment
Open

GC allocs for rendering #367

lucasmontec opened this issue Aug 11, 2023 · 1 comment

Comments

@lucasmontec
Copy link

lucasmontec commented Aug 11, 2023

I'm getting around half mb of GC allocs when rendering a component with just a few attributes. The asset also seems to be making assembly reloading sometimes slow, scaling somewhat badly as it grows in numbers.
Have you checked performance issues with a very large amount of attributes?

image

@lucasmontec
Copy link
Author

Its getting worse. I had to abandon the asset for 2 projects in my company. Unfortunately, it's blowing up with allocations (around 7MB per frame) on certain cases.
I’ve tracked it down to something with the serialized reference elements using PropertyField with showChildElements=true causing it to blow up.
Its something around the PropertyHandler.GetHeight() and the UseReorderabelListControl().
Its calling RuntimeFieldInfo.GetValue() lots of times.
There's a string format call that is called a lot and allocs a lot.
There's also a runtimeType.ToString allocation around .6MB per frame.

My team member reported over 100mb per frame.

profiler snapshot:
https://mega.nz/file/AA13wLbD#u_eao9JWr2eemvLwrORIIUkleapeIDe55eG2x8qQm4k

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