I'm not sure if this is a backend problem (something about the hierarchy code is silly, like making one request per subclass entity), or if it's a rendering problem (something in the AppNodeBadge is expensive?).
If there's lots of associations, but few subclasses, everything seems fine, so it does seem to be specific to the hierarchy API request or UI components.
example: http://dev.monarchinitiative.org/PATO:0000001
I'm not sure if this is a backend problem (something about the hierarchy code is silly, like making one request per subclass entity), or if it's a rendering problem (something in the AppNodeBadge is expensive?).
If there's lots of associations, but few subclasses, everything seems fine, so it does seem to be specific to the hierarchy API request or UI components.