In reply to warnerrs:
The problem with that advice is by the time you get to the point where performance is an issue and you run the profiler, you’ve already wasted more simulation time than it would have taken to write your own methods, and there are many template code generators out there that do this for you without having to incur a performance penalty.
Also, usually you don’t need these methods in uvm_component classes anyway since you never copy or compare these classes. But every field you add to the uvm_config_db with these macros adds to the overall performance penalty of all usage.