only short strings all data is formatted on the serverside
the base data has about 120 columns, but we're bringing it down to 10-20
ish, but this still makes qx sluggish
about 20000 rows, but we're using blocks so only about 200 rows are
actually on the browser at anytime.
on my screen i visually see about 30 rows, and 7 columns.
this means that for every single row scroll it rerenders about 600 cells
for a 20column table.which takes about 300ms
________________________________
From: Jim Hunter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 01, 2007 6:27 PM
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] qx.ui.table.Table with (too) many
columns
long amounts of code does not equate to more time. CSS Style
Sheets are slower to process then inline code is. You never did let us
know what your idea of a large grid is. How many rows? How many columns?
What sort of data is in the grid, numbers, short strings, very long
strings? Images? There could be many reasons you are seeing a slow down,
we need to get to the root of the problem.
Jim
www.D4PHP.org
www.D4PHP-Hosting.com
On 8/1/07, Bart van der Werf <[EMAIL PROTECTED]> wrote:
I've been looking at what qx generates.
the following was the element for a single gridcell
"""
<div
style="position:absolute;left:100px;top:0px;width:100px;height:15px;over
flow:hidden;white-space:nowrap;border-right:1px solid
#eeeeee;border-bottom:1px solid
#eeeeee;padding-left:2px;padding-right:2px;cursor:default;-moz-user-sele
ct:none;">5</div>
"""
Does it really need to be this big?
Would it be faster if i would creates css styles with a
shortname and use those for the common cases instead of this long
sequence for every cell ?
greets, Bart
________________________________
From: Bart van der Werf [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 01, 2007 10:10 AM
To: qooxdoo Development
Subject: [qooxdoo-devel] qx.ui.table.Table with
(too) many columns
I'm having some performance issues,
We are using a very large grid and the number of
columns is causing qx to become very slow.
At the top of the profiling results of venkman
profiler are:
72000ms qx.ui.table.cellrenderer.Default
updateDataCellElement
: function(cellInfo, cellElement)
22000ms qx.ui.table.pane.Pane
_updateContent_orig
: function(completeUpdate, onlyRow,
onlySelectionOrFocusChanged)
No other function comes above 5000 ms.
Is it possible to have the same block like
behaviour for columns as allready is supported for rows ?
greets, Bart
------------------------------------------------------------------------
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?
Stop.
Now Search log events and configuration files using AJAX
and a browser.
Download your FREE copy of Splunk now >>
http://get.splunk.com/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
