Best practice - number of queues

What are best practices for the number of queues that RT should have or
can handle without noticeably degrading page refreshes? To give you
some background to this question: I have read through RT Essentials.
In the first few chapters, it is mentioned that from an administrative
standpoint it is best to have as few queues as needed. When considering
the scenario where the request tracker wants to keep track of tickets by
customer, is it best to?:

  • Create a queue for each customer
  • Create a custom field called ‘Customers’
  • Just generate reports for the billing department based on sending
    domain

Any other options?

David Smithson

ActivSupport, Inc.
Your Flexible IT Partner
Microsoft Gold Partner – Small Business Specialist
http://www.activsupport.com
Director of Technical Services
Direct: (415) 869 2991