When using an authorization strategy other than Unsecured or FullControlOncedoggedIn if there are 10,000+ jobs tied to labels, the tag cloud makes rendering the individual node screens seriously unresponsive as there are repeated access checks of read permission when counting the number of jobs with which to scale the tag cloud.

It is not necessary to run the permission checks in order to return the count of jobs, and additionally it is not necessary to build a list of all jobs and then sort the list before filtering and then throwing away the list and retaining the count.

A specialized count function with a denormalized loop should provide more usable performance... additionally it is questionable whether the tag cloud provides much utility for very large installations.