It has come to my attention that the lag on the main CFUK server has become a bit of a problem halting progress in projects due to bot movement and block placing lag. My suspicion to the lag is a spawner or an area with a tonne of entities. To find out how this is occurring I would like to see who on the server has a large enough thing to cause this lag.(Note this is not just me experiencing the lag others are)
Though it is not urgent I would advise anyone with a large or high output of entity creator to perhaps turn it off for say 3 days and see if there is a difference.

THE LAG IS REAL

Yours lagging
Timeno

Timeno, it may of been direwolf sucking all the resources.

I've made a few changes on the server, could you try now?

ok sounds like an answer

Seems the server is still lagging rather severely. I keep having lag rollbacks of up to 15 seconds

I've just had a quick play on the Vanilla Server, and I was getting the occasional bit of block lag. At the time I was the only one on that server, and 4 people were on the DW20 server.

I'm on a completely undeveloped island (and unclaimed until now!)

On another note, I have found that Spruce Doors don't work with Lockette

Yeah there definetally seems to be a resource issue with DW20, It drops multiple player connections while a couple manage to stay online so i can see why vanilla would be experiencing issues while DW is running.

I'm currently taking notes of what sort of enviroments/conditions seem to effect things more however at this point around 8-10 players seem to be a server killer. A few players online earlier affected the connection more than others, most likely due to heavy machinery/gens/quarries etc.

For now though id say (regrettably) that unless the player count is reduced to say no more than 5 on at a time or we donate more so broons can upgrade again for DW, I dont think it's going to last as it's affecting more than just it's own portion.
There may however be something specifically that's causing the lag like on old tekkit or original FTB. For the moment we can continue to do ingame and server research to see if something shows up.

I'm not saying that you should abandon your builds because the world may not last, only that the problems aren't confined to DW as such we may need to make some choices soon so people can still play even in vanilla.

As for the doors on vanilla it's due to the coding/block ID on those doors being slightly different from vanilla doors so lockette hasn't been programmed to include them yet. Might be an update for it or a way to manually add them to the configs.

I don't know if it helps but when I get disconnected it is always with the connection timed out error!

Lag should be low/none on the vanilla server, the DW server has a much lower cpu priority.

To clarify what I said before, on the vanilla server I was experiencing no lag most of the time, with the occasional lag spike (mostly when people logged in / out, but sometimes just randomly here or there.)

One thing I just thought of is that people have probably forgotten (or don't know of) the old rule for modified servers - please switch off your machines when you are logged out of the game. I seem to remember this being an issue for crashes and lag on some of the modified servers in the past.

Yeah, i've been restating that rule to players on DW recently. Unfortunately nothing much has helped. There are a couple of memory leaks and some Resource hogging scripts. Apparently "Journey map server side data collection" is one of them.

Supposedly there is going to be a DW update soon to fix most of the lag issues.

FWIW it may be worth checking your connection to the server too as its not always the server's fault. OK maybe 90% of the time it is but...Some time ago I found that my outgoing traffic was routed via an unreliable peering link. After much complaining in a public forum eventually the route changed and the connection improved a lot.

Another thing is that I found that the Monster server I played on after the CF one died (oops) had a big problem with going unresponsive at regular-ish intervals. My suspicion was that it might have been Java "garbage collection" at work.

I wouldn't get too hung up about the machines thing though, the chunks should just unload.

They "should" unload but quarries still chunkload when running and if under a base etc then that would mean all the other machines are also loaded.

It's mainly a precaution at this point. I think possibly 12 hourly restarts should help gut out the garbage (mem leaks etc) for a while until something is updated to fix some problems. According to Piggles, the server was running quite well after it completely died and was restarted so it's possible this may be an option.

Restarts can sometimes cause a few issues with the world but as far as i've read through research if you run a stop then restart command on the server there's only approx 2% chance of world corruption vs 30% odd chance. But of course those are on servers that dont have broons at the helm

Oh yeah I forgot about quarries because they'd been banned where I was playing. I did get odd piles of entities from time to time, so I'd still say watch out for chunk boundries when setting out machines.

ender quarries are the preferred quarry atm since they only load a max of 2 chunks at a time regardless of the size, it only loads the chunk it sits in and the chunk its working on and will also stop when there is no space in the attached inventory (instead of spewing out items like the bc quarry).

Aye, it's slower but it's a hell of a lot more server friendly.

slower? HAH! mine can clear the full 16 chunks in a few mins..... i just haven't given it enough power to do that yet.... i mean 150k RF/t was my max for 2mins