![]() It’s likely to impact to dashboard performance. Remove unused datasets from analysisĭatasets that may have been used in the past but have no visual associated with the dashboard anymore add to the metadata payload unnecessarily. We recommend the following actions regarding metadata. MetadataĪs seen in the preceding execution sequence, QuickSight fetches metadata up front for a given dashboard during the initial load. We recommend using SPICE whenever possible. ![]() Utilizing the capabilities of SPICE when possible is a great way to boost overall performance because SPICE manages scaling as well as caching results for you. Now let’s look at many great tips that can improve your dashboard’s performance! SPICE Performance may also be slightly different based on the browser type because each browser handles contention differently. Many of the steps run in the end-user’s browser, therefore there are limitations such as the number of sequences and workloads that can be pushed onto the browser. Many operations run in parallel and all visual-related queries are run via WebSocket, as shown in the following screenshot. SPICE, cardinality of fields and how often data is getting refreshed etc. The actual execution is more complex and depends on how dashboards are configured and other factors such as the data source types, Direct Query vs. Pagination within visuals may lead to additional queries. If you’re using SPICE, the concurrency of queries is much higher. Up to your concurrency limit, the queries to render your visuals run in a specific sequence (described later in this post).Queries are performed, which may include setting up row-level and column-level security, or fetching dynamic control values, default parameters, and all values of drop-downs in filter controls.All the metadata (such as visual configurations and layout) is fetched for the dashboard.A request is triggered in the browser, leading to several static assets such as JavaScript, fonts, and images being downloaded.Let’s look at the general execution process to understand the implications: The following diagram illustrates the data flow: Dashboards built against direct query data sources may require provisioning or managing infrastructure on the customer side. This is a fully managed service-you don’t need to worry about provisioning or managing infrastructure when you want to scale up a particular dashboard from tens to thousands of users on SPICE. The web server, QuickSight engine, and SPICE are auto scaled by QuickSight. SPICE uses a combination of columnar storage, in-memory technologies enabled through the latest hardware innovations, and machine code generation to run interactive queries on large datasets and get rapid responses. The data flow in QuickSight starts from the client browser to the web server and then flows to the QuickSight engine, which in some cases executes queries against SPICE-a Super-fast, Parallel, In-memory Calculation Engine-or in other cases directly against the database. Data flow and execution of QuickSight dashboard loads QuickSight automatically optimizes queries and execution to help dashboards load quickly, but you can make your dashboard loads even faster and make sure you’re getting the best possible performance by following the tips and tricks outlined in this post. Amazon QuickSight is cloud-native business intelligence (BI) service.
0 Comments
Leave a Reply. |