Frans Bouma's blog

(This is a stub, which redirects to the article on the LLBLGen Pro blog. I've stopped blogging LLBLGen Pro full articles here and instead do that on the new LLBLGen Pro blog. I post a small post here to notify readers the post is over there :) )

(This is a stub, which redirects to the article on the LLBLGen Pro blog. I've stopped blogging LLBLGen Pro full articles here and instead do that on the new LLBLGen Pro blog. I post a small post here to notify readers the post is over there :) )

After a two week beta period, we’ve released LLBLGen Pro v5.5! To see what’s new, please visit the New features page on our website or go to the beta announcement blog post which lists all the small changes in one place.

Last Friday we’ve released LLBLGen Pro v5.5 beta! We expect to release the RTM in a week or two. Below is the list of what’s new in this release. I’ll describe some of the new features in more detail in articles in the coming weeks. The main focus was on our own ORM framework, the LLBLGen Pro Runtime Framework, this time around.

Today we’ve released LLBLGen Pro v5.4! This release comes packed with a lot of small enhancements and some bigger ones. See below for the full list of changes. This update is a free update for all users with an active subscription. 

In this post I’ll discuss some memory optimization work I’ve done recently on the LLBLGen Pro runtime framework, v5.3.2. This is a popular (commercial) .NET ORM. LLBLGen Pro is on the market since 2003 and has seen a lot of refactoring work internally over the years, among them performance optimizations and memory usage optimizations. With new features come new challenges to make the overall framework perform the same or even faster and still perform the new features as well, so optimizing the core engine is a recurring effort.

For some time now I maintain the RawDataAccessBencher repository on github, and once in a while I run the suite of benchmarks and post the results. In the benchmarks I included all major micro-ORM and full ORM frameworks for .NET which have a significant group of users. The benchmarks are typical ‘micro’ benchmarks in that they run for a relatively short period of time. They also focus solely on fetch performance, how fast the given framework can create a query, fetch the resultset from the database server (on another machine on the network) and materialize objects from the resultset.