Mustafa,

This may be a problem with the backend query code!  If you're returning the 
correct subset of rows based on start & end index, maybe your sort algorithm is 
inefficient.  For a dataset that large, make sure you are using table indexes 
and they are actually being used in the query.  Also, you should use a query 
that actually returns the subset of rows instead of looping through the whole 
dataset to get the rows you need.

HTH,

    Gene  

Burak Arslan <burak.ars...@arskom.com.tr> wrote:

>
>Hello Mustafa,
>
>My experience is that, such huuuge data sets are too difficult to 
>navigate with just a  table and a scrollbar anyway. (the scrollbar gets 
>too sensitive) So I introduce additional fields around the table to let 
>the user do some more filtering, whenever we need to deal with high 
>amounts of data.
>
>Maybe one should be able to group rows[1], or introduce pagination[2,3], 
>like in ext js' grid component. While i think such features provide nice 
>eye-candy, i doubt that they  improve the data navigation experience.
>
>Best,
>Burak
>
>
>[1]: http://www.extjs.com/deploy/dev/examples/grid/grouping.html
>[2]: http://www.extjs.com/deploy/dev/examples/grid/sliding-pager.html
>[3]: http://www.extjs.com/deploy/dev/examples/grid/paging.html
>
>MartinWittemann wrote:
>> Hey,
>> we havent tested the remote table with such a huge amount of rows. But
>> basically that should work. Could you please open a bug report for that so
>> we keep in mind that we need to profile that?
>> Regards,
>> Martin
>>
>>
>> info-211 wrote:
>>   
>>> Good morning list
>>>
>>> Want to know were the limit for remote table is? Have handle a dataset  
>>> from 1.7 till 3.5 millions rows. My script hangs and ff asks me to  
>>> stop the script. Were is the limit, and why does it takes to long to  
>>> handle the data virtualy? I mean the table just loading 200 rows at  
>>> once?
>>>
>>> Regards Sak
>>>
>>> Von meinem iPhone gesendet
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Verizon Developer Community
>>> Take advantage of Verizon's best-in-class app development support
>>> A streamlined, 14 day to market process makes app distribution fast and
>>> easy
>>> Join now and get one step closer to millions of Verizon customers
>>> http://p.sf.net/sfu/verizon-dev2dev 
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> qooxdoo-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>>     
>>
>>   
>
>
>------------------------------------------------------------------------------
>This SF.Net email is sponsored by the Verizon Developer Community
>Take advantage of Verizon's best-in-class app development support
>A streamlined, 14 day to market process makes app distribution fast and easy
>Join now and get one step closer to millions of Verizon customers
>http://p.sf.net/sfu/verizon-dev2dev 
>_______________________________________________
>qooxdoo-devel mailing list
>qooxdoo-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to