title: Best practice table in SAPUI5
body: <p>I already used <code>sap.m.Table</code> directly with OData and also with <em>JSON</em>. But what is the best practice to display let's say 500+ items with for example 7 columns.
  Should I load the OData into a local <em>JSON</em> Model or use OData directly with growing functionality (pagination)?</p>
  
  <p><strong>[edited version + research below]</strong></p>
  
  <p>According to the API of <a href="https://sapui5.hana.ondemand.com/#docs/api/symbols/sap.m.Table.html" rel="nofollow noreferrer">sap.m.Table</a> </p>
  
  <ul>
  <li><blockquote>
    <p>... For mobile devices, the recommended limit of table rows is 100 (based on 4 columns) to assure proper performance. To improve initial rendering on large tables, use the growing feature</p>
  </blockquote></li>
  </ul>
  
  <p>According to the API of <a href="https://sapui5.hana.ondemand.com/#docs/api/symbols/sap.ui.table.Table.html" rel="nofollow noreferrer">sap.ui.Table</a> </p>
  
  <ul>
  <li><blockquote>
    <p>Provides a comprehensive set of features for displaying and dealing with vast amounts of data.</p>
  </blockquote></li>
  <li><blockquote>
    <p>the Table control reuses its DOM elements of the rows. When the user scrolls, only the row contexts are changed but the rendered controls remain the same</p>
  </blockquote></li>
  </ul>
  
  <p>So one has to work with the growing functionality anyway?</p>