I didn’t say it was evil, and I didn’t say to never do anything on tick, I said performance issues add up quickly, and your post only supports that fact. I also said gets are cheap and he wouldn’t have to worry about them, which your post also supports, 1550 for a 3ms cost is measurable, but it sure is cheap.
1550 ticking actors with only just get actor location are making a quite more so notable dent than ones ticking without a dent. The case of someone just putting a simple get on event tick and nothing more is very rare.
I wonder how much those numbers change if you add some math in there, throw in a simple division and see how much that affects these numbers. Gets should barely have a measurable cost but math operations are different, I’m actually kinda curious just how much more 1550 divisions per second would cost.
You’re spot on about using the profiler to troubleshoot performance issues though, I also quite like the gpu visualizer.