Somebody pointed us to the same problem we the same solution in uNhAddIns.Personally I saw some difference, in production, in a stress-tests (usage of CPU) but I'm not completely sure that the problem was only LinFu DynamicProxy. The real problem of LinFu, IMO, is this: http://code.google.com/p/linfu/people/list
<http://code.google.com/p/linfu/people/list>Try to think which is the problem. 2009/8/10 srf <[email protected]> > > Moving to nhibernate 2.1 from 1.2 I noticed a performance problem > doing proxying and I ended up noticing that castle dynamic proxy uses > the .net Type builder and the type build seems to have a bug where its > gets prgressivly slower the more types created. We have 300 different > types in our domain model and it would proxy 100 types pretty fast but > by the time it proxys the 200th type , the Type builder was taking > over 10 seconds to create a new type. We also run under mono and it > actually runs a lot faster since it doesnt have this same performance > problem. Maybe microsoft should see what the mono people are doing to > help with that. > At any rate, I switch to using LinFu and it had none of these > performance problems as was way faster and so far everything seems to > work so I was thinking of just switching our production environment to > use linfu but was wondering if others use linfu in production with > nhibernate and if anyone has had any problems with it? > > thanks > > scott > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
