<?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 Please share best practices about optimizing responsiveness for heavy Visual Analytics Reports in SAS Visual Analytics</title>
    <link>https://communities.sas.com/t5/SAS-Visual-Analytics/Please-share-best-practices-about-optimizing-responsiveness-for/m-p/989141#M18992</link>
    <description>&lt;P&gt;We are experiencing a long waiting time in sophisticated reports in terms of parameter usage, linked objects, big tables, aggregated measures and tables and filters.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The admin team is working on implementing solutions and pushing towards upgrading to the latest release.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But I need SAS experts to share best practices.&lt;/P&gt;
&lt;P&gt;I imagine and somehow have experienced the following do's and don'ts. But it is more gut feeling than real evidence:&lt;/P&gt;
&lt;P&gt;Good practices and common sense:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Apply data source filter when possible (sometimes it's disabled, under what circumstances?) and use a parameter for the filter condition.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Avoid VA joined tables if it could be done in the ETL SAS code section&lt;/LI&gt;
&lt;LI&gt;Do not carry unnecessary columns in the report's tables&lt;/LI&gt;
&lt;LI&gt;Use varchar for the tables' columns if possible&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;But I do not know if using a slider for a timestamp column with 100k distinct values on the top of the page slows down the report.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or which calculated items consume a lot of compute, like string operations.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or ¡f linked actions used throughout the report can cause latency.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 03 Jun 2026 10:19:08 GMT</pubDate>
    <dc:creator>acordes</dc:creator>
    <dc:date>2026-06-03T10:19:08Z</dc:date>
    <item>
      <title>Please share best practices about optimizing responsiveness for heavy Visual Analytics Reports</title>
      <link>https://communities.sas.com/t5/SAS-Visual-Analytics/Please-share-best-practices-about-optimizing-responsiveness-for/m-p/989141#M18992</link>
      <description>&lt;P&gt;We are experiencing a long waiting time in sophisticated reports in terms of parameter usage, linked objects, big tables, aggregated measures and tables and filters.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The admin team is working on implementing solutions and pushing towards upgrading to the latest release.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But I need SAS experts to share best practices.&lt;/P&gt;
&lt;P&gt;I imagine and somehow have experienced the following do's and don'ts. But it is more gut feeling than real evidence:&lt;/P&gt;
&lt;P&gt;Good practices and common sense:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Apply data source filter when possible (sometimes it's disabled, under what circumstances?) and use a parameter for the filter condition.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Avoid VA joined tables if it could be done in the ETL SAS code section&lt;/LI&gt;
&lt;LI&gt;Do not carry unnecessary columns in the report's tables&lt;/LI&gt;
&lt;LI&gt;Use varchar for the tables' columns if possible&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;But I do not know if using a slider for a timestamp column with 100k distinct values on the top of the page slows down the report.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or which calculated items consume a lot of compute, like string operations.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or ¡f linked actions used throughout the report can cause latency.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2026 10:19:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Visual-Analytics/Please-share-best-practices-about-optimizing-responsiveness-for/m-p/989141#M18992</guid>
      <dc:creator>acordes</dc:creator>
      <dc:date>2026-06-03T10:19:08Z</dc:date>
    </item>
    <item>
      <title>Re: Please share best practices about optimizing responsiveness for heavy Visual Analytics Reports</title>
      <link>https://communities.sas.com/t5/SAS-Visual-Analytics/Please-share-best-practices-about-optimizing-responsiveness-for/m-p/989143#M18993</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;The items you included are all good practice. I believe that in the past, high-cardinality prompts were a performance issue and we made a fix. I am not sure how much they affect performance today. I am also not sure about the specific case of date sliders, I think they might be less of an issue than a discrete control like a drop-down list.&lt;BR /&gt;&lt;BR /&gt;We should probably add some tips to the documentation, so I will watch this thread.&lt;BR /&gt;&lt;BR /&gt;Sam</description>
      <pubDate>Wed, 03 Jun 2026 12:27:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Visual-Analytics/Please-share-best-practices-about-optimizing-responsiveness-for/m-p/989143#M18993</guid>
      <dc:creator>Sam_SAS</dc:creator>
      <dc:date>2026-06-03T12:27:41Z</dc:date>
    </item>
  </channel>
</rss>

