There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
Querying content type by name is inefficient
Almost all content queries in Orchard have a join on the content type table that is queried by name, using an IN operator. When there is only one type, it would be considerably more efficient to use = rather than IN, but a first and very effective mitigation
of this problem is to create an index on the content type name.
I was able to bring the time for one specific particularly affected query from 7s down to 10ms.