even one primitive node in tick is a heavy calculation, because it runs N times per second, when N is your FPS. Tick is there for either prototyping before optimizing, debugging, and calling functions relevant to frame swapping.
I know there is a bunch of tutorials online that use Tick for everything, but these are made primarily by content creators rather than engineers. in 95% of the cases, there is a much better alternative to Tick events.
Take a look at this amazing video by Parrish from Epic for further details: