﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on It Is Called Humor</title><description>@Moira,
  
Allow me to assume that this is a matter of not knowing how to use NHibernate properly, rather than a fault in NHibernate itself.
</description><link>http://ayende.com/2547/it-is-called-humor#comment2</link><guid>http://ayende.com/2547/it-is-called-humor#comment2</guid><pubDate>Sat, 16 Jun 2007 14:26:19 GMT</pubDate></item><item><title>Moira commented on It Is Called Humor</title><description>&gt; Hibernate is meant for use in scalable, high performance 
  
&gt; applications. 
  
  
I just tried a test with 20 tables, using nhibernate and using rdmbs the way I am supposed to.
  
  
I optimised nhibernate to be aware of the lot, but the same way I have a codegen that handles everything nhibnernate would do.
  
  
Hibernate scaling is awful, it does not even look like it could pass basic functional requrements for most scenarios. It introduces stacks of dependancies, and performance is nowhere close (50 times slower).
  
  
If that is what it was meant for, it certainly failed.
</description><link>http://ayende.com/2547/it-is-called-humor#comment1</link><guid>http://ayende.com/2547/it-is-called-humor#comment1</guid><pubDate>Sat, 16 Jun 2007 14:03:46 GMT</pubDate></item></channel></rss>