Is it because it has to scan all actors to find the class you’re requesting?
Or is it because it has to scan through all the items in the class you’re requesting?
I guess another way to frame this question would be ‘Is it more reasonable to use GAAOC when you know you’ll only have a single matching actor as opposed to hundreds?’ Or would the performance cost of the function be the same, regardless?
Interesting… so I’ve actually been learning about reference optimization a lot lately.
Are you saying that because the GAAOC function creates a hard reference itself(?), why not? Because once you’ve used GAAOC, there’s no additional ‘reference cost’ to store the results as a variable?
It’s actually not that bad from a performance perspective, I thought it would iterate through all actors in the world, but nope, it uses the hash to severely limit the amount of actors it needs to iterate over.
That said, the use of the node should still never be a requirement to get the references. Maybe if you have a novel use-case to do some one-off behavior I can see justifying the use of the node, but otherwise, I’d just manage the references.
If you’re using the node because you don’t know how to otherwise get the references, you should really learn to manage references. Once you know, then you should also have a feel for when you really should be managing your references.