The question asks for evaluating virtual warehouse performance impacted by query queuing. While ACCOUNT_USAGE.QUERY_HISTORY (B) provides query-level queuing metrics like QUEUED_OVERLOAD_TIME, INFORMATION_SCHEMA.WAREHOUSE_LOAD_HISTORY (C) is specifically designed for warehouse-level performance analysis. It includes columns like AVG_QUEUED_LOAD (average number of queries queued due to warehouse overload) and AVG_QUEUE_PROVISION (queries queued during provisioning), which directly measure the impact of queuing on warehouse performance. The community discussion shows strong support for C (48% votes, multiple upvoted comments explaining warehouse-level analysis), with some support for B (52% votes). However, C is more targeted for warehouse performance evaluation, while B focuses on individual query analysis. Resource monitor (A) manages warehouse scaling but doesn't provide historical queuing analysis, and WAREHOUSE_METERING_HISTORY (D) tracks credit usage, not queuing impact.