Hello, After your "CreateBar();" call, clear your session from entities you have juste created and persisted (since you do not want to use a stateless session). That means add a "Session.Clear();" line in your test case after the "CreateBar();" line.
This suppress the performance trouble, and it looks normal to me. I have not studied your java test case to see what is the difference. Either you do something different that already cause the session to be cleared in java case, or Hibernate does it himself on transaction commit, not NHibernate. (Or maybe the java Hibernate has a far more better first level cache ? But I would be surprised that loading thousands of objects in memory without ether discarding them does not impact java hibernate too.) Anyway, with your .Net case without the session clear, you accumulate loads of entities in first level cache, causing the session to lose more and more time managing its cache. Side note : I have not used your binary references (paranoid mode), but mine, which are NHibernate 3.3.2 (+attribute downloaded from sourceforge targetting an older version but working with this one too), without mono and sqllite dependencies, using a sql express 2008 R2 db instead, and redefining the indexed text to be 1000 long (for it can not be indexed if longer that 8000 in sql server). Regards. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/groups/opt_out.
