I added about 70 categories to my repository and the module now takes over 20 seconds to load.  (Even entering the webpage takes over 20 seconds to load. )

So for testing purposes, I removed about 40 categories (30 remains) and the load time is now about 4 seconds.  I removed an additional 20 categories (10 remains) and the load time is about 1.5 seconds.

so I am now sure that the more categories one adds, the slower the module. 

However, I really do need to have over 70 categories for what I do.  Yet I can't have the load time be over 20 seconds or users will get the impression it doesn't work and will just leave my site.

Any ideas on how I can solve this problem??? 

you can probably fix it by adding some indexes to the database

I would look into adding indexes on 'ObjectID' and 'CategoryID' in the 'grmRepositoryObjectCategories' tables

and for Attributes try adding an index on 'ValueID' in the 'grmRepositoryObjectValues' table

correction...

My previous post said there was no improvement.  Acutally, I should not say that because I now have very little categories/attributes in my repository to really notice any major difference even if that was the reason.

  let me do more testing (by adding more categories and then adding/removing the index to see how it effects the load time.)

In the mean time, can you think of any other tables that may slow down the repository.  Perhaps  the table(s) that stores the actual categories/attributes?  What are the names of those tables??  (I am thinking I may need to index thoes tables too- if not already done) ?? Thanks