1. We are using .Net Framework 3.0/2.0 and LLBLGen 2.0. What's the best LLBLGen version we can upgrade to? We want to upgrade with less changes to the code.
2. Is there any adapter setting that can improve the performance while using PreFetch or with the latest versions?
3. Is there a way to remove TOP from a scalar query expression?
4. In general we are looking for performance enhancement that can be achieved using any logic / settings in using LLBLGen.

TrueBlue wrote:

1. We are using .Net Framework 3.0/2.0 and LLBLGen 2.0. What's the best LLBLGen version we can upgrade to? We want to upgrade with less changes to the code.

upgrading to a higher version always comes with some set of breaking changes. In general these are not that hard to overcome, and are all documented in the v2.6 documentation ("Migrating your code"). I'd migrate to v2.6, which is free for you (see customer area)

1. Is there any adapter setting that can improve the performance while using PreFetch or with the latest versions?

You can tweak the queries with DataAccessAdapter.ParameterisedPrefetchPathThreshold

Prefetch paths try to do their best in fetching the graph, however there are situations where you might want to fetch things manually, because it can't be done efficiently using prefetch paths, like using a limit on child nodes.

1. Is there a way to remove TOP from a scalar query expression?

This is implemented in v2.6

1. In general we are looking for performance enhancement that can be achieved using any logic / settings in using LLBLGen.

To gain performance, first profile your application, then check whether you have the most efficient code / algorithm in place where hot spots are located, then fix the hotspots. In LLBLGen Pro, if you issue a query, the query is ran for you, so any query which makes things slower is originating from your code, so look into that to limit the amount of queries executed, look into Excluding fields (so you don't fetch blob/image fields if you don't need them) and only fetch the data you need.

V2.6 has a much lower memory footprint and is faster than 2.0. Just download the installer and see for yourself You can install 2.6 side-by-side with 2.0, just realize that when you double click a .lgp file and save it in 2.6 you cant open it in 2.0

Thanks for the reply Otis. Appreciate that.