Mekanism chunkloads every single chunk it is in at all time causing horrible performance no matter what the forgechunkloading configs are

Forge: 14.23.5.2811
Mekanism: 1.12.2-9.6.3.355(and many older versions had the same issue)

Could you please provide your evidence of this? I can assure you it doesn't explicitly do it and the Anchor Upgrade itself uses Forge's chunkloading system

Please update to the latest Mekanism release and send me your forcedchunks.dat files (note that there may be one for each dimension).

It's impossible to say what might be causing it - it may not even be Mekanism.

I'll get your evidence if i can later, but the server does spam this literally like a thousand times on startup
[06:29:27] [Server thread/FATAL] [FML]: The mod mekanism attempted to force load a chunk with an invalid ticket. This is not permitted.

That's with version 353 though but imma say it anyways incase you didn't fix that yet

That message has been fixed, but in fact has the opposite effect to your claim, it means the chunks weren't reloaded on startup for those that had anchor upgrades

We do not have like a thousand anchor upgrades at all, id be suprised if we even have 10 it is just a small private test server xD
I can log off, come back later and suddenly see like 200k redstone etc extra while i have no anchor upgrades.
Perhaps it is caused by cables etc connecting chunks?

Was discussed outside of Github, nothing explicitly Mekanism was found