2010/7/29 zonkzen <[email protected]>: > There's still two questions: > 1. Since now I have only one Session, all nHibernate objects are > attached to it ( despite the FlushMode.Never, but it's by design ). > Question is really not precise and kind of stupid, cause it's hard to > measure, but how many objects can be attached to session till I will > start feeling it's something that slows app down? Are there any hard > numbers or benchmarks I can do? Anything that can help me on that? How much work do you plan to do in a single request? A request is one call to render a web page or one call to a web service. Unless you have large tree-like structures, the performance of first level cache can be completely neglected. If you have issues, it would be rather beneficial to use Ayende's NHProfiler to look for (n+1)-queries and other more impacting issues.
> 2. On page: > http://using.castleproject.org/display/AR/Enable+Session+per+Request > , there's this sentence: > "NOTE: Often ASP.NET will process HTTP requests for items such as > images through the Begin/End page lifecycle. This is fixable via > changing the configuration, however this technique injects a safe- > guard." I can only maje an educated guess here: Web Forms has life cycles for every control on the page. If you use a Scope in your OnButtonClickedAndHurray()-code-behind-ASPX-pages, other controls may ask for AR objects outside of that scope. SpR guards against it by using a single scope for the whole page lifecycle. -Markus -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. 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/castle-project-users?hl=en.
