Re: [hibernate-dev] Runtime efficiency: sharing some profiling output

>> # DefaultEntityAliases.intern >> Why are we interning this? >> org.hibernate.loader.DefaultEntityAliases.intern(String[]) >> If they are constants, I guess they could be reused rather than >> re-computed all the time.. in fact, see next point: >> >> # Aliases and other string generations >> It seems Hibernate ORM is generating property aliases and other little >> Strings all the time; this test isn't using any HQL, just direct >> loading of entities via primary keys or by following relations from >> other managed entities. > > > Isn't there a point where interning becomes wasteful? Surely there must be. > What is that tipping point? I'm not suggesting to use interning; what surprised me is that even for standard load operations of an entity, Hibernate doesn't have a "prepared" set of alias names; couldn't the metamodel for each entity contain pre-computed alias names (or full SQL strings) to do the basic CRUD operations on that entity? Not being familiar with this code, I just found it odd that to load the same entity type some million times it would recompute these alias strings over and over.