[flexcoders] Re: using a repeater with large data sets
Good idea Trac! I'll use the count and startingIndex properties to manage the paging locally ;) Kind regards, Andrew Spaulding www.flexdaddy.info --- In flexcoders@yahoogroups.com, "Tracy Spratt" <[EMAIL PROTECTED]> wrote: > One possibility with the repeater is to set the number of items that are > rendered, then, instead of scrolling, use page-up, page-down buttons. A > repeater with around a hundred moderately complex items is horribly > slow. Show only 10, and recycleChildren and things improve > dramatically. This is much simpler to impement that true server-based > data paging, though Matt C. has a good discussion of that. > > A cellRenderer in a list is faster than the repeater, but with 100+ > items still takes several seconds. > > No matter how you do it, it is the rendering that takes the time. > > Tracy > > -Original Message- > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Andrew Spaulding > Sent: Thursday, July 07, 2005 7:36 PM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] using a repeater with large data sets > > Hi all, > > I am currently using a repeater to display a list of search results, > each of them being a container of sorts with a custom header with > extra controls. Click on the header open and closes the result, a long > with a few other bits and pieces. > > One thing I have found is that with a larger search result listing it > takes quite some time to render the results. > > If I was to manually create the search result children myself using > createChild etc (rather than using the repeater) what effects would > this have on my performance issues? I am not particularly interested > in paging result sets just yet, but this would be my next step if I am > unable to speed things up otherwise. > > Any thoughts would be appreciated, > > Cheers, > > Andrew Spaulding > www.flexdaddy.info > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
[flexcoders] Re: using a repeater with large data sets
Hi Alex, Yeh I followed your posts on performace with large data sets, and our return data from the RemoteObject service is relatively fast. The problem lies with the rendering of the results. For what I'm doing I have found the the Repeater works better for me compared to a List with a CellRenderer (and yes I already have the repeated contents extracted into a separate mxml file). I have gone with Tracy's idea, and am using the 'count' and 'startingIndex' property on the Repeater. I am currently putting together a paging component, kind of like how Google would page its search results, and am having this control the Repeater. Thanks to everyone for there help, Andrew www.flexdaddy.info --- In flexcoders@yahoogroups.com, Alex Cruikshank <[EMAIL PROTECTED]> wrote: > Hi Andrew, > If you're using remoting, I'd make sure your performance problems > aren't with the serialization/deserialization of the results before > you invest much time in optimizing the display. I've done some > research into this > (http://www.carbonfive.com/community/archives/2005/07/the_remoting_de.html) > and the performance of calls returning large lists can be quite poor > even when the app server call is snappy. This is true even when the > results aren't displayed at all. > > I recommend using a List, Horizontal List, or Tile list with a paging > data provider for anything that may have over 50 or so items. Once > you get your data provider working, a repeater is surprisingly easy to > convert to a list. You just need to extract the contents of the > repeater into a separate mxml (if they're not already), give the new > mxml a setValue() method, and set the cell renderer of the list to the > new mxml. > > Hope this helps, > Alex > > > On 7/7/05, Andrew Spaulding <[EMAIL PROTECTED]> wrote: > > Good idea Trac! > > > > I'll use the count and startingIndex properties to manage the paging > > locally ;) > > > > Kind regards, > > > > Andrew Spaulding > > www.flexdaddy.info > > > > > > > > --- In flexcoders@yahoogroups.com, "Tracy Spratt" <[EMAIL PROTECTED]> wrote: > > > One possibility with the repeater is to set the number of items that are > > > rendered, then, instead of scrolling, use page-up, page-down buttons. A > > > repeater with around a hundred moderately complex items is horribly > > > slow. Show only 10, and recycleChildren and things improve > > > dramatically. This is much simpler to impement that true server-based > > > data paging, though Matt C. has a good discussion of that. > > > > > > A cellRenderer in a list is faster than the repeater, but with 100+ > > > items still takes several seconds. > > > > > > No matter how you do it, it is the rendering that takes the time. > > > > > > Tracy > > > > > > -Original Message- > > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > > > Behalf Of Andrew Spaulding > > > Sent: Thursday, July 07, 2005 7:36 PM > > > To: flexcoders@yahoogroups.com > > > Subject: [flexcoders] using a repeater with large data sets > > > > > > Hi all, > > > > > > I am currently using a repeater to display a list of search results, > > > each of them being a container of sorts with a custom header with > > > extra controls. Click on the header open and closes the result, a long > > > with a few other bits and pieces. > > > > > > One thing I have found is that with a larger search result listing it > > > takes quite some time to render the results. > > > > > > If I was to manually create the search result children myself using > > > createChild etc (rather than using the repeater) what effects would > > > this have on my performance issues? I am not particularly interested > > > in paging result sets just yet, but this would be my next step if I am > > > unable to speed things up otherwise. > > > > > > Any thoughts would be appreciated, > > > > > > Cheers, > > > > > > Andrew Spaulding > > > www.flexdaddy.info > > > > > > > > > > > > > > > -- > > > Flexcoders Mailing List > > > FAQ: > > http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > > Search Archives: > > > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > > Yahoo! Groups Links > > > > > > > > > > > > -- > > Flexcoders Mailing List > > FAQ: > > http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > > > > > > > > > YAHOO! GROUPS LINKS > > > > > > Visit your group "flexcoders" on the web. > > > > To unsubscribe from this group, send an email to: > > [EMAIL PROTECTED] > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. > > > > > > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexco
[flexcoders] Re: using a repeater with large data sets
Ah ofcourse, the 'PageSelector' component you wrote. I remember reading the articles a long time back when you first wrote them, but in this scenario I wasn't interested in server side paging. I'll check out the component, thanks, Andrew www.flexdaddy.info --- In flexcoders@yahoogroups.com, "Matt Chotin" <[EMAIL PROTECTED]> wrote: > My blog post from way back has an example of that control (well the > files that come with the example) > > > > http://weblogs.macromedia.com/mchotin/archives/2004/03/large_data_sets.c > fm > > > > Matt > > > > > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Andrew Spaulding > Sent: Thursday, July 07, 2005 10:09 PM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: using a repeater with large data sets > > > > Hi Alex, > > Yeh I followed your posts on performace with large data sets, and our > return data from the RemoteObject service is relatively fast. The > problem lies with the rendering of the results. > > For what I'm doing I have found the the Repeater works better for me > compared to a List with a CellRenderer (and yes I already have the > repeated contents extracted into a separate mxml file). > > I have gone with Tracy's idea, and am using the 'count' and > 'startingIndex' property on the Repeater. I am currently putting > together a paging component, kind of like how Google would page its > search results, and am having this control the Repeater. > > Thanks to everyone for there help, > > Andrew > www.flexdaddy.info > > > --- In flexcoders@yahoogroups.com, Alex Cruikshank <[EMAIL PROTECTED]> wrote: > > Hi Andrew, > > If you're using remoting, I'd make sure your performance problems > > aren't with the serialization/deserialization of the results before > > you invest much time in optimizing the display. I've done some > > research into this > > > (http://www.carbonfive.com/community/archives/2005/07/the_remoting_de.ht > ml) > > and the performance of calls returning large lists can be quite poor > > even when the app server call is snappy. This is true even when the > > results aren't displayed at all. > > > > I recommend using a List, Horizontal List, or Tile list with a paging > > data provider for anything that may have over 50 or so items. Once > > you get your data provider working, a repeater is surprisingly easy to > > convert to a list. You just need to extract the contents of the > > repeater into a separate mxml (if they're not already), give the new > > mxml a setValue() method, and set the cell renderer of the list to the > > new mxml. > > > > Hope this helps, > > Alex > > > > > > On 7/7/05, Andrew Spaulding <[EMAIL PROTECTED]> wrote: > > > Good idea Trac! > > > > > > I'll use the count and startingIndex properties to manage the > paging > > > locally ;) > > > > > > Kind regards, > > > > > > Andrew Spaulding > > > www.flexdaddy.info > > > > > > > > > > > > --- In flexcoders@yahoogroups.com, "Tracy Spratt" <[EMAIL PROTECTED]> > wrote: > > > > One possibility with the repeater is to set the number of items > that are > > > > rendered, then, instead of scrolling, use page-up, page-down > buttons. A > > > > repeater with around a hundred moderately complex items is > horribly > > > > slow. Show only 10, and recycleChildren and things improve > > > > dramatically. This is much simpler to impement that true > server-based > > > > data paging, though Matt C. has a good discussion of that. > > > > > > > > A cellRenderer in a list is faster than the repeater, but with > 100+ > > > > items still takes several seconds. > > > > > > > > No matter how you do it, it is the rendering that takes the time. > > > > > > > > Tracy > > > > > > > > -Original Message- > > > > From: flexcoders@yahoogroups.com > [mailto:[EMAIL PROTECTED] On > > > > Behalf Of Andrew Spaulding > > > > Sent: Thursday, July 07, 2005 7:36 PM > > > > To: flexcoders@yahoogroups.com > > > > Subject: [flexcoders] using a repeater with large data sets > > > > > > > > Hi all, > > > > > > > > I am c
Re: [flexcoders] Re: using a repeater with large data sets
Hi Andrew, If you're using remoting, I'd make sure your performance problems aren't with the serialization/deserialization of the results before you invest much time in optimizing the display. I've done some research into this (http://www.carbonfive.com/community/archives/2005/07/the_remoting_de.html) and the performance of calls returning large lists can be quite poor even when the app server call is snappy. This is true even when the results aren't displayed at all. I recommend using a List, Horizontal List, or Tile list with a paging data provider for anything that may have over 50 or so items. Once you get your data provider working, a repeater is surprisingly easy to convert to a list. You just need to extract the contents of the repeater into a separate mxml (if they're not already), give the new mxml a setValue() method, and set the cell renderer of the list to the new mxml. Hope this helps, Alex On 7/7/05, Andrew Spaulding <[EMAIL PROTECTED]> wrote: > Good idea Trac! > > I'll use the count and startingIndex properties to manage the paging > locally ;) > > Kind regards, > > Andrew Spaulding > www.flexdaddy.info > > > > --- In flexcoders@yahoogroups.com, "Tracy Spratt" <[EMAIL PROTECTED]> wrote: > > One possibility with the repeater is to set the number of items that are > > rendered, then, instead of scrolling, use page-up, page-down buttons. A > > repeater with around a hundred moderately complex items is horribly > > slow. Show only 10, and recycleChildren and things improve > > dramatically. This is much simpler to impement that true server-based > > data paging, though Matt C. has a good discussion of that. > > > > A cellRenderer in a list is faster than the repeater, but with 100+ > > items still takes several seconds. > > > > No matter how you do it, it is the rendering that takes the time. > > > > Tracy > > > > -Original Message- > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > > Behalf Of Andrew Spaulding > > Sent: Thursday, July 07, 2005 7:36 PM > > To: flexcoders@yahoogroups.com > > Subject: [flexcoders] using a repeater with large data sets > > > > Hi all, > > > > I am currently using a repeater to display a list of search results, > > each of them being a container of sorts with a custom header with > > extra controls. Click on the header open and closes the result, a long > > with a few other bits and pieces. > > > > One thing I have found is that with a larger search result listing it > > takes quite some time to render the results. > > > > If I was to manually create the search result children myself using > > createChild etc (rather than using the repeater) what effects would > > this have on my performance issues? I am not particularly interested > > in paging result sets just yet, but this would be my next step if I am > > unable to speed things up otherwise. > > > > Any thoughts would be appreciated, > > > > Cheers, > > > > Andrew Spaulding > > www.flexdaddy.info > > > > > > > > > > -- > > Flexcoders Mailing List > > FAQ: > http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > Yahoo! Groups Links > > > > > > -- > Flexcoders Mailing List > FAQ: > http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > > > > YAHOO! GROUPS LINKS > > > Visit your group "flexcoders" on the web. > > To unsubscribe from this group, send an email to: > [EMAIL PROTECTED] > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. > > > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
RE: [flexcoders] Re: using a repeater with large data sets
My blog post from way back has an example of that control (well the files that come with the example) http://weblogs.macromedia.com/mchotin/archives/2004/03/large_data_sets.cfm Matt From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Andrew Spaulding Sent: Thursday, July 07, 2005 10:09 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: using a repeater with large data sets Hi Alex, Yeh I followed your posts on performace with large data sets, and our return data from the RemoteObject service is relatively fast. The problem lies with the rendering of the results. For what I'm doing I have found the the Repeater works better for me compared to a List with a CellRenderer (and yes I already have the repeated contents extracted into a separate mxml file). I have gone with Tracy's idea, and am using the 'count' and 'startingIndex' property on the Repeater. I am currently putting together a paging component, kind of like how Google would page its search results, and am having this control the Repeater. Thanks to everyone for there help, Andrew www.flexdaddy.info --- In flexcoders@yahoogroups.com, Alex Cruikshank <[EMAIL PROTECTED]> wrote: > Hi Andrew, > If you're using remoting, I'd make sure your performance problems > aren't with the serialization/deserialization of the results before > you invest much time in optimizing the display. I've done some > research into this > (http://www.carbonfive.com/community/archives/2005/07/the_remoting_de.html) > and the performance of calls returning large lists can be quite poor > even when the app server call is snappy. This is true even when the > results aren't displayed at all. > > I recommend using a List, Horizontal List, or Tile list with a paging > data provider for anything that may have over 50 or so items. Once > you get your data provider working, a repeater is surprisingly easy to > convert to a list. You just need to extract the contents of the > repeater into a separate mxml (if they're not already), give the new > mxml a setValue() method, and set the cell renderer of the list to the > new mxml. > > Hope this helps, > Alex > > > On 7/7/05, Andrew Spaulding <[EMAIL PROTECTED]> wrote: > > Good idea Trac! > > > > I'll use the count and startingIndex properties to manage the paging > > locally ;) > > > > Kind regards, > > > > Andrew Spaulding > > www.flexdaddy.info > > > > > > > > --- In flexcoders@yahoogroups.com, "Tracy Spratt" <[EMAIL PROTECTED]> wrote: > > > One possibility with the repeater is to set the number of items that are > > > rendered, then, instead of scrolling, use page-up, page-down buttons. A > > > repeater with around a hundred moderately complex items is horribly > > > slow. Show only 10, and recycleChildren and things improve > > > dramatically. This is much simpler to impement that true server-based > > > data paging, though Matt C. has a good discussion of that. > > > > > > A cellRenderer in a list is faster than the repeater, but with 100+ > > > items still takes several seconds. > > > > > > No matter how you do it, it is the rendering that takes the time. > > > > > > Tracy > > > > > > -Original Message- > > > From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On > > > Behalf Of Andrew Spaulding > > > Sent: Thursday, July 07, 2005 7:36 PM > > > To: flexcoders@yahoogroups.com > > > Subject: [flexcoders] using a repeater with large data sets > > > > > > Hi all, > > > > > > I am currently using a repeater to display a list of search results, > > > each of them being a container of sorts with a custom header with > > > extra controls. Click on the header open and closes the result, a long > > > with a few other bits and pieces. > > > > > > One thing I have found is that with a larger search result listing it > > > takes quite some time to render the results. > > > > > > If I was to manually create the search result children myself using > > > createChild etc (rather than using the repeater) what effects would > > > this have on my performance issues? I am not particularly interested > > > in paging result sets just yet, but this would be my next step if I am > > > unable to speed things up otherwise. > > > > > > Any thoughts would be apprecia
