1st thing about performance problems is: measure it. So attach a profiler and check where the bottlenecks are. Before that it's useless to discuss this any further. Also without details about your code / version of llblgen pro used etc. it's also useless to discuss further.
Once identified, analyze what's going on: a query which fetches 100,000 entities into memory will take a while, a very complex join over 10 tables with each millions of rows will take a while etc. Look into optimizing the logic which creates the bottleneck with for example more clever algorithms, different approaches etc.
You also don't give any information about anything in your system, so I don't really see why we're the cause of the problem. For what's worth, we do analysis of our code with every version to see how to make it faster and more efficient. With every version we've optimized bottlenecks away and made memory footprints lower, also added tweaking options for developers so they can optimize the queries executed, e.g. by using excluding fields, paging etc. Where we could, we did optimize the logic with more clever algorithms, re-using objects etc. However there's a limit to what we can do without compromising functionality, however that's not a problem actually, queries in general execute much longer than the logic used to create them.
It also is unclear whether you're talking about the designer or the runtime framework. For example we did fix a performance issue in the SQL Server driver of 3.0 recently. Also, if you're using Oracle and connecting to a db takes a long time, check whether your TSN names are set up properly.
But in short: we need more info.
I moved the thread to general.