We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
I have two dragons on a server. They standing on the mountain and do nothing.
Yet, i could see that they causing about 4% of server lag. Narrowing down Spark profile I could see that it ended up with FluidloggedAPI calls
Logs debug.zip
Additional context Happening on modpack E2E-E
Is it normal that idle dragons consume so much CPU? Is there options of FluidloggedAPI that could decrease this lag?
Same happens on Fluidlogged-API-v2.2.7 too https://spark.lucko.me/RTBKVibM7A
Fluidlogged-API-v2.2.7
The text was updated successfully, but these errors were encountered:
fix(mods): 🔴Remove FluidloggedAPI
FluidloggedAPI
3158ac8
Sadly, but FluidloggedAPI caused small but notable TPS load (about 5%) More info: [[1]](https://github.com/jbredwards/Fluidlogged-API/issues/184)[[2]](https://github.com/jbredwards/Fluidlogged-API/issues/182)
Has this issue been fixed? I have also discovered this issue
Sorry, something went wrong.
I dont know since i removed FluidloggedAPI.
jbredwards
No branches or pull requests
Describe the bug
I have two dragons on a server. They standing on the mountain and do nothing.
Yet, i could see that they causing about 4% of server lag. Narrowing down Spark profile I could see that it ended up with FluidloggedAPI calls
https://spark.lucko.me/TDejgIdx2Q
Logs
debug.zip
Additional context
Happening on modpack E2E-E
Is it normal that idle dragons consume so much CPU? Is there options of FluidloggedAPI that could decrease this lag?
Update:
Same happens on
Fluidlogged-API-v2.2.7
too https://spark.lucko.me/RTBKVibM7AThe text was updated successfully, but these errors were encountered: