Running into a big problem with this mod's map component tick, it's pretty big and likely would put it on the slow mods list[docs.google.com] if anyone's actually updating that thing. using dubs analyzer

it appears to update every pawns priorities every like, idk 300 or so ticks where it spikes to 54 or more ms for me with 20 colonists. the average for me with 20 seems to be 1.5ms average but mostly spikes, this is huge as most map components average less than 0.05ms

if you could make it so on each of these ticks it updates only 1 pawn and cycles through them you could get away with updating more often but overall slower per pawn for a smoother play time.

If instead it's more about the bigger updates like do pops need tending or checking supplies etc, then you could divide those checks to spread out over time instead of cycling through pawns and could even do both if they're both processing hogs.

most of the lag occurs in Rimworld.Pawn_workSettings:SetPriority(probably like 95% of it, it's hard to figure out an average when it spikes every few seconds) so this would be to refactor code if you'd like to try from that angle.

Also i noticed it does this even with all pawns asleep, you might be able to find a way of skipping updating the sleeping pawns

NOTE: I wrote all of this while investigating and found that worktab has a patch that makes the mapcomponent take about 6 times longer than without it(probably as it updates the subtasks). Removing the mod put it down to average of .22-.27 but still spikes to 35ms occasionally but usually only takes 4-5ms. this is still pretty beefy, and any reduction here will likely have a relative reduction to those using worktab, so I thought I wouldn't delete what I found so far as it could still greatly improve performance and make for a smoother experience.

I'll likely keep using worktab as this mod still has the problem that only work tab really fixed for me. having a single pawn who specifically prioritizes hauling to blueprints reduces construction times by like 7 and that's really important when recovering from assaults and the like.

Note Note, i'm going to continue testing tomorrow but I noticed that the call has 2 humps[i.imgur.com] one near the beginning and one near the end, when the super spikes happen the spike is near the end of the second hump.

Tomorrow I'll probably update how toggling free will changes things.