Moved Too Quickly, Can't Allocate RAM?

Previously ran a 1.16.5 Forge Server with 200+ mods and had no issue allocating ram and running without any lag. Allocated 12G of RAM for the server (32G available)

I now updated to a 1.18.1  (39.0.8) Forge Server and downsized to about 30 Mods.

my user_jvm_args are as followed:

# Xmx and Xms set the maximum and minimum RAM usage, respectively.
# They can take any number, followed by an M or a G.
# M means Megabyte, G means Gigabyte.
# For example, to set the maximum to 3GB: -Xmx3G
# To set the minimum to 2.5GB: -Xms2500M

# A good default for a modded server is 4GB.
# Uncomment the next line to set it.
-Xmx10G

The run batch is as follows

REM Forge requires a configured set of both JVM and program arguments.
REM Add custom JVM arguments to the user_jvm_args.txt
REM Add custom program arguments {such as nogui} to this file in the next line before the %* or
REM  pass them to this script directly
java @user_jvm_args.txt @libraries/net/minecraftforge/forge/1.18.1-39.0.8/win_args.txt nogui%*

With only myself logged in to the server, flying in a straight line I get "Player moved too quickly" and i get a rubber banding effect. The server memory usage in task manager will not exceed 6200M.

Is there something I am doing wrong with my memory allocation in the args? Is this "moved too quickly" and rubber banding unavoidable in the current version?

Edited December 31, 20213 yr by UndeadOne
added symptom