On server load, obviously larger servers will eat more storage and more memory, and take longer to load, but, surely they mean fewer loads?
In practice, do larger sectors means less frequent loading, or are there other reasons why this isn't what happens?
A player exists in the center sector of a 27 sector box. 3 by 3 by 3 sectors. There are two sides to the coin.
One side is that the size of the box equals the contents of the box. The bigger the sector the more chunks are in it. The more server resource it takes to load them. Times 27!
There is also the clients maximum distance render setting. The higher you set that the harder your PC has to work. And the same goes for the server with larger sectors.
The other side is movement that goes over a sector border. Causing the next 9 sectors to load. Every time you do that there is some lag as stuff loads in and other sectors unloads. The server can get very busy if you do that one after the other in a short time frame. Think stuff like fights and high speed travel.
The maximum server speed setting is also important here as that helps to limit the frequencies of going from sector to sector.
The best way of travel from a server stand point is no movement of your own. Just jumps from your jump drive. Then the server has to only load the sectors and not your relative motion to the stuff within the sector.
Now i hear everybody scream yeah chain drives for the win. No sorry no tango. They enable repeated jumps in a short time frame. And there lays the problem. The jumps are way to fast after another. The server can not keep up with the loading and unloading of sectors and goes into desync. It chokes on it and keeps trying to process it all stalling the server CPU at 100% and causing a server crash.
There is no global sweet spot for sectors. It all depends on what your server CPU is capable of and how much you want to hurt it.