I was under the impression that all BEAM processes had the same footprint but reading up on timers, it looks like that isn’t the case?
Just curious if there are other types of processes that are different than “normal” Erlang processes, e.g. schedulers, NIFs.
There’s only one kind of process and they all have the same basic footprint.
The stuff about the timer module refers to all of its timers being handled by a single process (the timer server), which can become a bottleneck in large systems. There’s nothing special about this process per se, it’s just an ordinary process that the module spawns to handle its timers.