Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You could do a lot of things, I will just list them in order that will give you the best impact.</p> <ol> <li><code>FlexTable</code> is not meant for 300 rows. Since your table is so simple, you should consider generating the HTML by hand, and then using simple HTML widget. Also, 300 rows is <strong>a lot</strong> of information - consider using pagination. The <a href="http://gwt.google.com/samples/DynaTable/DynaTable.html" rel="noreferrer">DynaTable sample app</a> shows you how to do this.</li> <li>It looks like you are using one GWT module per page. That is the wrong approach to GWT. Loading a GWT module has some non-trivial cost. To understand what I mean, compare browser refresh on gmail v/s the refresh link that gmail provides. That is the same cost you pay when every page in your website has a distinct GWT module.</li> <li>If the list of candidates is needed across views, you can send it along with the HTML as a JSON object, and then use the <a href="http://code.google.com/webtoolkit/doc/latest/DevGuideI18n.html#DevGuideDynamicStringInternationalization" rel="noreferrer">Dictionary class</a> in GWT to read it. This saves you the RPC call that you are making. This approach is only recommended if the data is going to be useful across multiple views/screens (like logged in users info)</li> <li>Check how long your RPC method call is taking. You can enable <a href="http://code.google.com/webtoolkit/doc/latest/DevGuideLightweightMetrics.html" rel="noreferrer">stats in GWT</a> to figure out where your application is taking time. </li> <li>You can also run <a href="http://code.google.com/webtoolkit/speedtracer/" rel="noreferrer">Speed Tracer</a> to identify where the bottleneck is. This is last only because it is obvious FlexTable is performing a lot of DOM manipulations. In general, if you don't know where to start, Speed Tracer is a great tool.</li> </ol>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload