[Dbix-class] Using Class::Std under-the-hood

[Dan Kubb]

> What are the performance implications of using Class::Std?

 From Class::Std docs:

   "Of the several popular methods of reliably enforcing  
encapsulation in Perl,
   inside-out objects are also by far the cheapest. The run-time  
performance of
   inside-out classes is effectively identical to that of regular  
hash-based
   classes. In particular, in both schemes, every attribute access  
requires only
   a single hash look-up. The only appreciable difference in speed  
occurs when
   an inside-out object is destroyed."

And later Damian says:

   "There is a simple, convenient, and utterly secure way to prevent  
client code
   from accessing the internals of the objects you provide. Happily,  
that approach
   also guards against misspelling attribute names (a common error in  
hash-based
   classes), as well as being just as fast as--and often more memory- 
efficient
   than--ordinary hash-based objects."

As fast as -- and *more* memory efficient. ;)

> One of the things that make DBIx::Class promising is the reduced  
> overhead as
> compared to Class::DBI. If the fundamental building blocks are  
> changed to
> something that greatly increases the overhead, I personally do not  
> see a net
> gain. Yes, I like encapsulation, etc, etc.

The truth is that if we use something other than blessed hash objects
there is going to be some overhead.  If we are concerned about  
optimizing
attribute lookups we should look into an array based object instead.

Will there be any appreciable difference in performance either way?  I
doubt it, especially when compared with the other operations being  
performed
by DBIx::Class.

--

Dan Kubb