TiltedFloste

Hey, i think i know what your problem is (it was mine too on a 7x7 Grid). -> Leave at least 4 ports free between the next port, ATLAS is also using the ports around the defined one. For example your query-ports: 10000 10005 10010 10015 10020 and so on... then traveling should work as expected ^^ And we using different seamless ports too without problems (we have the problem that grids are sometimes crashing on travel (process freezes at 100%), but this is another error...)

Same here at our server... 5 servers with 14 CPU-Cores and 64 GB-RAM each and got the same problems. The CPUs are running at 30-40% load normally (used RAM ~34 from 64 GB), but if some people are travelling and the grid crashes one core stucked at 100% until we stop the grid and start it again. Some players can travel without problems, and if some others are traveling they are crashing the grid... That sucks We have used every single thing to get a good performance (with TickRate and the day0 setting to 2018). We are on Ubuntu too (18.04 LTS)

This is an insane bug! Just set the Day0 to a date in 2018 and the load average went from 10+ down to ~5 on our servers, this is ridiculous...