This port still uses the 1.16 values for 1.18+ versions. Upstream uses the the number of available threads-1 as the amount of main worker threads, while this port currently uses the number of available threads/2, resulting in worse performance.
According to the original wiki (I am aware this is for fabric, but it's 1.16+ in general), it also appears that the thread priorities are different- using 5 and 3 instead of 5 and 1, however this doesn't seem to be reflected in the upstream code for some reason.

Yes, i've made these changes but i didn't released it yet.

Fixed in the new update.

Great, thanks!