Further update:
I set DEBUG level logging on anyway, then only set it for the NHibernate.AdoNet.Batcher. This gave me more information about how long each select was taking. For SQLServer the ExecuteReader was taking between 1ms and 10 ms then the DataReader was normally taking about 10ms but the first one took 1350ms. For SQLite the ExecuteReader varied massively between about 1ms and 5000ms and then the DataReader was taking between 20000 and 30000ms Could this be due to a lack of memory? After all, SQLServer is running on another machine, whilst SQLite is running as part of the IIS worker process. I have increased the amount of memory from 512Mb to 1Gb and this appears to have had no impact whatsoever. Looking at the CPU trace carefully, it is completely maxed out when running the DataReader and actually drops a bit when running the ExecuteReader (which presumably is the SQLite select) -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/o7US3cFjInAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
