I'm curious: what's the use case for pushing 15 million (or, heck, even 50,000) 
records to the client?


--- In flexcoders@yahoogroups.com, "iloveyouwisconsin" <iloveyouwiscon...@...> 
wrote:
>
> Maybe I'll have to wait until Flex 7 (or later) 'til they truly make flex 
> able to handle large datasets smoothly. (I guess I'll also have to advise 
> those at Adobe and the flex evangelists that what they define as a "large" 
> dataset isn't large in practice. They probably need to moonlight as interns 
> for a few of their customers to snapback into reality. There's no company in 
> the real world that would define a large dataset as only a few thousand items)
> 
> --- In flexcoders@yahoogroups.com, "iloveyouwisconsin" <iloveyouwisconsin@> 
> wrote:
> >
> > How many records is considered "too large" for a datagrid to handle? I am 
> > using Flex 4 with Zend AMF & paging enabled. When I google it the topic, 
> > most seem to think that a "few thousand" is large, but that doesn't seem 
> > hardly anything to me. I thought Zend would do the trick but it isn't 
> > anywhere near what I need. My 15 million records didn't go over too well (I 
> > can use the scroll wheel on my mouse to scroll through the records but it 
> > kept crashing when I tried to use the scrollbar on the datagrid to jump 
> > around). I ask because I don't want to have to jimmy around with code until 
> > I'm blue in the face trying to find something flex can handle. Can I do 1 
> > million? 5,000? 500,000? I just want to be able to let users play around w/ 
> > the scrollbar on the datagrid without it crashing, is all (though I realize 
> > that the user's machine will play a big factor in performance. All of my 
> > users have computers that are no more than a couple yrs old)
> > 
> > I also ask because I am sure others would like to know for their 
> > projects....is there a more efficient way to get the data than Zend, like 
> > Livecycle or Coldfusion? I am willing to switch the backend up a bit in 
> > order to increase performance of my app.
> > 
> > 
> > many thanks!
> >
>


Reply via email to