<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Quick Tips #10 - Slice n' Dice in Scalability</title>
    <link>https://community.qlik.com/t5/Scalability/Quick-Tips-10-Slice-n-Dice/m-p/1497439#M1544</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Times New Roman; font-size: 12pt;"&gt; &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times New Roman; font-size: 12pt;"&gt; &lt;/SPAN&gt;&lt;SPAN style="mso-bidi-font-family: Calibri; color: #000000; font-size: 12pt; mso-ansi-language: EN-US; font-family: Calibri; mso-bidi-theme-font: minor-latin;"&gt;Slicing an application into smaller parts will reduce the need for resources even if the same amount of data is loaded into RAM.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Times New Roman; font-size: 12pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 10pt;"&gt;&lt;SPAN style="mso-bidi-font-family: Calibri; color: #000000; font-size: 12pt; mso-ansi-language: EN-US; font-family: Calibri; mso-bidi-theme-font: minor-latin;"&gt;The hard part is to find the dimension best suited for slicing. Slicing into too many slices can cause the ratio of UI versus data to become inefficient. To prevent this one might introduce a new "grouping-dimension". States can be grouped in north, south, east and west.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 10pt;"&gt;&lt;SPAN style="mso-bidi-font-family: Calibri; color: #000000; font-size: 12pt; mso-ansi-language: EN-US; font-family: Calibri; mso-bidi-theme-font: minor-latin;"&gt;Combining this with section access will further improve the situation. Even splitting a file in two slices will have a positive effect on resource usage. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Times New Roman; font-size: 12pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 10pt;"&gt;&lt;SPAN style="mso-bidi-font-family: Calibri; color: #000000; font-size: 12pt; mso-ansi-language: EN-US; font-family: Calibri; mso-bidi-theme-font: minor-latin;"&gt;Cheers from the Scalability Team.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Times New Roman; font-size: 12pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 15 Dec 2011 14:07:28 GMT</pubDate>
    <dc:creator>lse</dc:creator>
    <dc:date>2011-12-15T14:07:28Z</dc:date>
    <item>
      <title>Quick Tips #10 - Slice n' Dice</title>
      <link>https://community.qlik.com/t5/Scalability/Quick-Tips-10-Slice-n-Dice/m-p/1497439#M1544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Times New Roman; font-size: 12pt;"&gt; &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times New Roman; font-size: 12pt;"&gt; &lt;/SPAN&gt;&lt;SPAN style="mso-bidi-font-family: Calibri; color: #000000; font-size: 12pt; mso-ansi-language: EN-US; font-family: Calibri; mso-bidi-theme-font: minor-latin;"&gt;Slicing an application into smaller parts will reduce the need for resources even if the same amount of data is loaded into RAM.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Times New Roman; font-size: 12pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 10pt;"&gt;&lt;SPAN style="mso-bidi-font-family: Calibri; color: #000000; font-size: 12pt; mso-ansi-language: EN-US; font-family: Calibri; mso-bidi-theme-font: minor-latin;"&gt;The hard part is to find the dimension best suited for slicing. Slicing into too many slices can cause the ratio of UI versus data to become inefficient. To prevent this one might introduce a new "grouping-dimension". States can be grouped in north, south, east and west.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 10pt;"&gt;&lt;SPAN style="mso-bidi-font-family: Calibri; color: #000000; font-size: 12pt; mso-ansi-language: EN-US; font-family: Calibri; mso-bidi-theme-font: minor-latin;"&gt;Combining this with section access will further improve the situation. Even splitting a file in two slices will have a positive effect on resource usage. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Times New Roman; font-size: 12pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 10pt;"&gt;&lt;SPAN style="mso-bidi-font-family: Calibri; color: #000000; font-size: 12pt; mso-ansi-language: EN-US; font-family: Calibri; mso-bidi-theme-font: minor-latin;"&gt;Cheers from the Scalability Team.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Times New Roman; font-size: 12pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Dec 2011 14:07:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/Quick-Tips-10-Slice-n-Dice/m-p/1497439#M1544</guid>
      <dc:creator>lse</dc:creator>
      <dc:date>2011-12-15T14:07:28Z</dc:date>
    </item>
  </channel>
</rss>

