|
Post by Polaris Seltzeris on May 14, 2020 4:58:54 GMT
I litterly already said what was causing the issue, it's a small disk bottleneck that spikes every once and a while. The best solution from my experience is to just turn off the server for like 10 minutes to let the disks catch up, then start it back up That isn't the best solution at all... you don't turn off the server for 10 minutes to let the disks catch up, clearly something is not optimized correctly.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 14, 2020 10:00:10 GMT
I litterly already said what was causing the issue, it's a small disk bottleneck that spikes every once and a while. The best solution from my experience is to just turn off the server for like 10 minutes to let the disks catch up, then start it back up That isn't the best solution at all... you don't turn off the server for 10 minutes to let the disks catch up, clearly something is not optimized correctly. we used to actually have auto restarts every 3 hrs or something
|
|
_Windows
Club 4000 Member
Posts: 7,881
| Likes: 9,611
|
Post by _Windows on May 14, 2020 12:05:33 GMT
I litterly already said what was causing the issue, it's a small disk bottleneck that spikes every once and a while. The best solution from my experience is to just turn off the server for like 10 minutes to let the disks catch up, then start it back up That isn't the best solution at all... you don't turn off the server for 10 minutes to let the disks catch up, clearly something is not optimized correctly. Exactly. Something is doing filesystem accesses too often for this to happen. Its better to do fewer larger IO ops than more smaller ones. At least on HDDs.
|
|
Video
Forum Admin
An op's rights activist
Posts: 5,585
| Likes: 5,893
IGN: VideoGameSmash12, videogamesm12
Old IGN: https://namemc.com/profile/VideoGameSmash12.2, https://namemc.com/profile/videogamesm12.1
Discord: Video#9801
Birthdate (MM/DD): 07/16
Timezone: UTC-07:00
Member is Staff. Need immediate assistance? Send a PM
|
Post by Video on May 14, 2020 15:09:45 GMT
That isn't the best solution at all... you don't turn off the server for 10 minutes to let the disks catch up, clearly something is not optimized correctly. Exactly. Something is doing filesystem accesses too often for this to happen. Its better to do fewer larger IO ops than more smaller ones. At least on HDDs. That's why I'm saying it might be columbus griefing, as it is often used to force servers to constantly load new chunks from disk.
|
|
|
Post by DragonSlayer2189 on May 14, 2020 15:28:13 GMT
Exactly. Something is doing filesystem accesses too often for this to happen. Its better to do fewer larger IO ops than more smaller ones. At least on HDDs. That's why I'm saying it might be columbus griefing, as it is often used to force servers to constantly load new chunks from disk. i know for a fact that its not columbus griefing because i monitor the loaded chunks of the server, but it could deffinitly be a problem of something needing filesystem access to much, we will have to ask @creeperseth to look into that
|
|
|
Post by Polaris Seltzeris on May 14, 2020 16:55:32 GMT
That isn't the best solution at all... you don't turn off the server for 10 minutes to let the disks catch up, clearly something is not optimized correctly. we used to actually have auto restarts every 3 hrs or something And we shouldn't have.
|
|
|
Post by Telesphoreo on May 14, 2020 18:15:06 GMT
ugh this is why we need a deployment system amirite guys xd Yes, so that we can manage/configure our dependencies and do proper QA testing on our server infrastructure to avoid these problems. Why do you guys insist on pooh poohing actual ideas that would make the server a whole lot more professional and thus address server stability? The fact is, I can go back a year ago and find these types of stability threads, and you'll see the development intellectuals (not just Telesphoreo here) criticizing me and others for even bringing up a possibility of solution to the problem. Yet why are we still having these conversations? Somebody needs to get their head out of the sand and actually put some effort in, because the fact that I have to repeat myself just about every week on a brand new thread shows how god awful this situation has been. What's also hilarious is that you recommend upgrading to the latest version of Paper right after sarcastically downplaying the idea of a deployment system. Gee, now why don't we have an out of date version of Paper? Huh... i- i- i was joking ma'am
|
|
|
Post by Polaris Seltzeris on May 14, 2020 18:18:30 GMT
Yes, so that we can manage/configure our dependencies and do proper QA testing on our server infrastructure to avoid these problems. Why do you guys insist on pooh poohing actual ideas that would make the server a whole lot more professional and thus address server stability? The fact is, I can go back a year ago and find these types of stability threads, and you'll see the development intellectuals (not just Telesphoreo here) criticizing me and others for even bringing up a possibility of solution to the problem. Yet why are we still having these conversations? Somebody needs to get their head out of the sand and actually put some effort in, because the fact that I have to repeat myself just about every week on a brand new thread shows how god awful this situation has been. What's also hilarious is that you recommend upgrading to the latest version of Paper right after sarcastically downplaying the idea of a deployment system. Gee, now why don't we have an out of date version of Paper? Huh... i- i- i was joking ma'am Then maybe you should try chipping in some effort to actually set up a deployment system?
|
|
|
Post by Telesphoreo on May 14, 2020 18:32:22 GMT
Then maybe you should try chipping in some effort to actually set up a deployment system? I have absolutely no control of development on the free OP server aside from making patches on GitHub to TotalFreedomMod. Everything is already running smoothly on SMP with no TPS drops, or out of date plugins. I'm super tight on disk space. The world takes up 60GB and the plugins take up even more. It's impossible for me to have two identical SMP testing servers due to the size of the server itself and I only have enough to host SMP. Plus, I highly doubt it would work with Pterodactyl.
|
|
|
Post by Polaris Seltzeris on May 14, 2020 18:44:30 GMT
Then maybe you should try chipping in some effort to actually set up a deployment system? I have absolutely no control of development on the free OP server aside from making patches on GitHub to TotalFreedomMod. Everything is already running smoothly on SMP with no TPS drops, or out of date plugins. I'm super tight on disk space. The world takes up 60GB and the plugins take up even more. It's impossible for me to have two identical SMP testing servers due to the size of the server itself and I only have enough to host SMP. Plus, I highly doubt it would work with Pterodactyl. Why don't we make an officialized team of people for the free OP server to set up quality assurance and deployment systems?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 15, 2020 1:57:20 GMT
That's why I'm saying it might be columbus griefing, as it is often used to force servers to constantly load new chunks from disk. i know for a fact that its not columbus griefing because i monitor the loaded chunks of the server, but it could deffinitly be a problem of something needing filesystem access to much, we will have to ask @creeperseth to look into that Sometimes the server freezes up and the resources are fine. I'll have to watch disk usage at this point.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 15, 2020 2:12:37 GMT
i know for a fact that its not columbus griefing because i monitor the loaded chunks of the server, but it could deffinitly be a problem of something needing filesystem access to much, we will have to ask @creeperseth to look into that Sometimes the server freezes up and the resources are fine. I'll have to watch disk usage at this point. I don't know if it helps but AWE has had problems recently. Also, whenever we run a WE it uses up 1gb of RAM.. I monitored it and I don't think it's normal
|
|
|
Post by Telesphoreo on May 15, 2020 2:19:18 GMT
Sometimes the server freezes up and the resources are fine. I'll have to watch disk usage at this point. I don't know if it helps but AWE has had problems recently. Also, whenever we run a WE it uses up 1gb of RAM.. I monitored it and I don't think it's normal AWE 3.7.0 and 3.7.1 have caused the SMP server to literally lock up and make it inoperable. The latest free version 3.6.20 works fine. Funny how the premium version cucks servers while the free one works perfectly.
|
|
|
Post by Polaris Seltzeris on May 15, 2020 2:21:08 GMT
Sometimes the server freezes up and the resources are fine. I'll have to watch disk usage at this point. Also, whenever we run a WE it uses up 1gb of RAM HUH
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 15, 2020 2:33:53 GMT
I don't know if it helps but AWE has had problems recently. Also, whenever we run a WE it uses up 1gb of RAM.. I monitored it and I don't think it's normal AWE 3.7.0 and 3.7.1 have caused the SMP server to literally lock up and make it inoperable. The latest free version 3.6.20 works fine. Funny how the premium version cucks servers while the free one works perfectly. scam alert ?
|
|