-
Notifications
You must be signed in to change notification settings - Fork 13
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
kCauldron - Report on performance of 0.2.0-dev1 #24
Comments
Thank you for taking the time to test and write about it =) I'm hoping to get rid of world leakage before the final release. Some things still hold a reference to the world after they are unloaded. I'm currently working on getting group reload to work. I want it to work correctly, as I want to allow for testing different group values without needing a full server restart(Which usually takes a while on modded servers.) The 'Entity removal de sync' is a weird bug, which should not happen. I will have to take a further look into that, as It can have lasting effects, by keeping a removed entity in the world(Even if it's marked as dead and will not tick). How much load was the server under while you tested? Did the Dynamic Ticking have to kick in by slowing stuff? |
I'd say I have a fairly healthy server (16GB ram, Java 8, ~3.5Gkz CPU's SSD) so it can handle almost everything. On purpose myself and some friends created some ticking tile entities (hoppers being activated via http://ftbwiki.org/Redstone_Clock) dropping into chests and those feeding into vanilla furnaces. Even did the worst thing you could think of - force create phantom chunk loading, or my favourite new term now - chunk churn ( if you want to read more about it https://www.reddit.com/r/feedthebeast/comments/3lfjpp/1710_post_mortem_investigating_mystery_chunk/ ) Only then did TickDynamic kick in and slow down the hoppers and furnaces. TPS was kept at around 17ish. Shudown, removed TickDynamic and as a test kept the same world and same setup and started the server up again. Ohh not good, TPS wise without TickDynamic was less then 10 before i killed the process via ssh LOL. I did say I did the worst thing you could think of server wise 👅 //offtopic but related I mentioned your mod here CyberdyneCC/Thermos#52 (comment) 😄 |
Hehe, Chunk Churn indeed. It seems then that it works as it should at least =D Thank you for your feedback! |
A side note - instead of giving releases as rar's you could upload the jar directly - this makes it easier to |
I'll give you my body If you can keep this alive. |
@Shybella I'll try to keep the kCauldron alive at least until FTB comes out with a stable 1.8 mod pack =) @spannerman79 Yeah, I'll do that for future releases. |
I think I have fixed the "Entity removal desync!" issue. This might also have caused other problems(Like world corruption in worst case, as the entity would still "exist", just be marked dead and not ticking) I'll do some more testing and probably release another KCauldron dev version soon. |
dev-3 released. Closing this issue. |
I've been running this on an actual "Open Beta" type server for awhile now. The label of Open Beta is so that my users know not to expect anything to stay the same and that there will be issues. Even
rm -rf world/
😈Overall;
Yes there is some world leakage but if anyone that runs kcauldron or a forge based server for longer then 6ish hours without restarting needs to be shot and buried lol
About the Group reload issue - I've known for quite some time that if you make any sort of config change its best to restart the server anyway. Give a chance for both mods and plugins to adapt to the new changes
The "Entity removal de sync!" console spam - reload fixes this and only happens when running your mod for the very first time and there was no config file for your mod to load. I consider that normal considering how the majority of other mods & plugins work - they won't work correctly on their maiden run 😛
Versions used: Both official via https://gitlab.prok.pw/KCauldron/KCauldron and the builds that you have access to @wildex999 😄
On both,
max-tick-time
for both ``tile&
entity` set to `1000`Noticeable issues:
None. Although a test of one server with average users of 20 (per day being online for longer then one hour) is not really a large enough test to mark an alpha release as beta
The text was updated successfully, but these errors were encountered: