BC pipes/excessive RAM

[Sepantari]

Hey guys,

I'm still pretty new to hosting a server, but i'm doing this for a couple of friends.
Since a few days some of the players have been using BC pipes to connect quarries to automated sorting and production systems.

Since the usage of the pipes the memory of my server went trought the roof. At first it would have 600 MB (6 players) in use.. now it is 1GB (1 player). How can this be? I suspect BC pipes and the fact that blocks travelling are kept in the RAM. Altough I'm not sure of this :/

Also I'm constantly getting info messages from my console. Any ideas on how to fix this or how much ram I should use to keep the server running with max. 10 players?

Spoiler

Spoiler

/SPOILER]

 

[11philip22]

i think you use more ram because there are more chunks being loaded

 

[Mr Chris]

Using around 1GB of RAM just having the server on is fairly typical. The reason you may have had less RAM usage at the start is since this is before users are generating chunks, placing machines, chunk loaders etc etc. To the best of my knowledge I do think that BC pipes can be a little laggy, but there shouldn't be much of a problem for a server of your size.

 

[Sepantari]

Using around 1GB of RAM just having the server on is fairly typical. The reason you may have had less RAM usage at the start is since this is before users are generating chunks, placing machines, chunk loaders etc etc. To the best of my knowledge I do think that BC pipes can be a little laggy, but there shouldn't be much of a problem for a server of your size.

I'm not using chunk loaders and we have covered enough ground in the first days of playing to create a world folder of around 400 MB XD so could it just be the quarries? I know there are players that have 3 of 'em running in a 64x64 setup..

 

[Mr Chris]

That could quite possibly be it Nothing you can do really unless you turn chunk loading for quarries off. Btw the info messages in the log are simply info messages, you dont need to worry about them at all.

 

[Sepantari]

That could quite possibly be it Nothing you can do really unless you turn chunk loading for quarries off. Btw the info messages in the log are simply info messages, you dont need to worry about them at all.

Does tuning this off have any consequences to the way the quarries work? And if not, how actually do I turn this off?
Because I've been thinking about setting a quarry limit per user (max 1 in a 32x32 setup) to reduce the chunks loaded, therefor not needing to buy a RAM upgrade from the host.

 

[Mr Chris]

The only effect of turning off quarry chunkloading off is that your users quarries will not work unless they are standing next/near to it. To turn it off find this in forgeChunkLoading.cfg and change the values to the following:

BuildCraft|Factory {
    # Maximum chunks per ticket for the mod.
    I:maximumChunksPerTicket=0
 
    # Maximum ticket count for the mod. Zero disables chunkloading capabilities.
    I:maximumTicketCount=0
}

Then save it, push it to the server and restart. Off the top of my head I dont think you can restrict the size of quarries so the only way you could do that is to simply tell your users that the max size is 32x32.

 

[Sepantari]

I think I found the problem and a solution. The quarries where F*ing op my RAM (there was one dude with 3 64x64 quarries). After he destroyed them and I restarted the server, the ram dropped to 520 MB with 3 people online. I also messaged the users and setup a MOTD saying they can only have 1 quarry per user with a max measurement of 32x32 (with penalties for not obeying the rules of-course).

Thanks for the quick reply's guys

 

[Mr Chris]

No problem