LCDS+CF DataManagement scalability is very very small

If there are huge data in target table, Java heap error happens. Even if you call fill method with parameters, Java heap error happens if the result data has many recordset.
# I tested by one million data or more.
Also it loads all data into Flex app on sort. You know it eats huge memory resource.
LCDS + CF DataManagement scalability is very very small. Don't use it with large data. Also there are a couple of critical bugs. The quality is not enough for real business. You'll have many troubles.
Second, under the hood this is using CFCs, and trying to do anything involving a million CFCs is also a very bad idea.
Third, you're using client-to-server paging, which loads the entire data set into memory. For a million objects, that's totally inappropriate. You should be using server-to-data paging, which loads the data on an as-needed basis.
As an aside, drop the number of letters in your captcha. 8 letters is going too far.
Huh, so I said "LCDS+CF DataManagement scalability is very very small". There is no way to control paging at CF side. The CFC of assembler doesn't have page method and only LCDS controls paging.
Also you know the benefits to use LCDS DataManagement . What you are talking about is "You can't use LCDS DataManagement with such huge data". It's same as my opinion.
You just can't use it with huge data sets on a single CPU license, using CFCs as the data objects, and using the simplified assemblers that CF exposes. I would hope that this doesn't come as a surprise to anyone.
I was under the impression that you were upset that you couldn't easily page through a million records on CF with the single-CPU LCDS. I'm hoping it's self-evident now why that is the case? But if I misunderstood you and you were just posting to make sure everyone else knows not try try and do this, then while I think that's really stating the obvious, I completely agree.
My image is pointing the following problems.
1. It can't control paging at CF side.
2. All data are loaded on sort.
I'm agreeing with you, I just think I'm missing the reason why this is somehow startling to anyone?