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] Configuration option access causes performance issue on spawner block ticking #127

Open
R00tB33rMan opened this issue Oct 15, 2024 · 2 comments

Comments

@R00tB33rMan
Copy link

Potential solution: Cache the configuration (on) fields to avoid map lookup.

image

Full report: https://spark.lucko.me/4kMcAEDqpF

@Esophose
Copy link
Member

Esophose commented Oct 15, 2024

I can at least confirm that isn't the cause of your TPS being 8, the hashmap lookups are mostly negligible. I'll consider inlining those settings since they show up at all, just know it wont make any noticeable performance difference

@R00tB33rMan
Copy link
Author

I can at least confirm that isn't the cause of your TPS being 8, the hashmap lookups are mostly negligible. I'll consider inlining those settings since they show up at all, just know it wont make any noticeable performance difference

Oh no, this isn't to infer that your resource is incurring major depreciation issues. We can handle a cap of ~600 concurrent on 1.21.1 @ 20 TPS. This was primarily due to all of the RTPs, among other things. We're just ensuring that your resource is as best as it can be. Better to report these issues and optimize 'em, despite their neglibility.

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

2 participants