CaveNightingale
commented
1 year ago Work as intended. DimensionalThreading need to wait until all worlds finish their world ticking in each game tick. That's why pthread_cond_wait is there. To find out which world is lagging, try to profile world threads. For example
/spark profiler --start --thread dimthread_overworld
/spark profiler --stop
I have a 1.19.2 fabric server with Dimensional Threading installed and I noticed that the server would have a small freeze every so often, so I used the spark profiler to see what it could be and I think "so.pthread_cond_wait" is making it freeze which is something Dimthread related. Any idea why this happens or/and how to fix it?
Any help would be greatly appreciated!