This counter reports how many distinct lockable resources, the named entities that locks are taken against, currently exist in the system. This is a related but distinct metric from the lock count itself, since one resource can have many locks against it, so tracking both helps the admin distinguish resource proliferation from simple lock contention. For example, an application that creates a new uniquely-named resource for every transaction instead of reusing a fixed set would drive this resource count up over time even if lock counts per resource stay low.