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

Iris's loadedRegions format Memory Usage Excessivity #1054

Open
R00tB33rMan opened this issue Nov 18, 2023 · 8 comments
Open

Iris's loadedRegions format Memory Usage Excessivity #1054

R00tB33rMan opened this issue Nov 18, 2023 · 8 comments

Comments

@R00tB33rMan
Copy link

Problem

We presently had roughly ~280 players online at the time of this heap. Although this is a lot of players, our heap still wound up retaining up to 37 GB in size, which is brutally high.

Here's an example of the issue:
image

Hopefully you can all manage to resolve this, as it's quite problematic!

We're using the latest release (3.0.0) iteration of Iris.

Solution

Rewrite loadedRegions logic and make it less aggressive and consumptive. We have over ~60 GB allocated to this instance, which should be more than enough.

Minecraft Version

1.21

Iris Version

3.0.0 for 1.19.2 - 1.20.2

Log

No Direct Link. Provided Above.

@RePixelatedMC
Copy link
Contributor

Yea ik im already working days on fixing the current source code made it better but it solved 1 problem of the 3 the system is having so its a improvement

@RePixelatedMC
Copy link
Contributor

Also this issue has been in iris since it got created lmao my guess is that tectonic plates didnt carry as much data as they do now so its only getting problematic since a year or 2

@R00tB33rMan
Copy link
Author

Understood. Hopefully we can get this resolved soon, as my instance/server would likely perform remarkably better, without this overhead. If any assistance is needed, do not hesitate to ask.

@RePixelatedMC
Copy link
Contributor

RePixelatedMC commented Nov 20, 2023

Pixeldev branch has improvements you could try and use that

@R00tB33rMan
Copy link
Author

Sorry for the late response! Running my fork with some other changes from other PR's, in addition to the latest changes from that branch. I'll let you know how it goes in the coming days!

@R00tB33rMan
Copy link
Author

Going to be honest: The new branches upon my testing and constant upstreams only made the situation worse and continually crashed my servers (or froze them) for long durations.

@RePixelatedMC
Copy link
Contributor

Known issue it are alpha releases i found a major flaw and am reworking the entire system for a month already or more

@RePixelatedMC
Copy link
Contributor

i havent prd it yet its all on my local branch the current branch is completely broken

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