Has anyone done performance comparisond for the framework (eg What is the performance compared to getting data straight from SQL server into a DATASET)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Obviously, doing handcrafted SQL will always be faster since there is none of the overhead associated with the mappings or processing associations, etc and you can fine tune the SQL to provide maximum performance.
I don't have hard figures, however the cost of the framework overhead in terms of a speed difference is actually fairly small if you set up your classes and mappings correctly, and if you think about what you are doing.
If you blindly create your classes, set everything to auto retrieve all the time, forget about proxy objects, etc then you can easily blow your performance to hell.
With all that said, the framework does allow you to use handwritten SQL (using object properties instead of SQL column names) if you have a particular need for performance and you don't mind tying yourself to some hardcoded SQL.
I don't think I need to mention the benefits side of using an O/R mapping framework (regardless of wether it is this one or something else).
- Richard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has anyone done performance comparisond for the framework (eg What is the performance compared to getting data straight from SQL server into a DATASET)
Obviously, doing handcrafted SQL will always be faster since there is none of the overhead associated with the mappings or processing associations, etc and you can fine tune the SQL to provide maximum performance.
I don't have hard figures, however the cost of the framework overhead in terms of a speed difference is actually fairly small if you set up your classes and mappings correctly, and if you think about what you are doing.
If you blindly create your classes, set everything to auto retrieve all the time, forget about proxy objects, etc then you can easily blow your performance to hell.
With all that said, the framework does allow you to use handwritten SQL (using object properties instead of SQL column names) if you have a particular need for performance and you don't mind tying yourself to some hardcoded SQL.
I don't think I need to mention the benefits side of using an O/R mapping framework (regardless of wether it is this one or something else).
- Richard