my first instinct is to have different engines for each schema, since
the model of a different engine per execution thread/request is very
common..the DynamicMetaData object accomplishes this. this might be
the quickest way to do it, but that creates a connection pool for each
schema; im
the method that I improved in my checkin is related to the mapper's
construction of a newly loaded instance, and the test case that
improves 20% focuses most of its time loading a list of 2500 items.
the test you have here spends a lot of time doing lots of other things,
such as saving items
