AWS QuickSight Best Practice for creating SPICE

0

Is it a best practice to create multiple SPICE databases for a single analysis and dashboard creation? Will this add significant monthly cost compared to creating only 1 big SPICE database?

ZeBron
질문됨 2년 전1388회 조회
2개 답변
0

HI, First of all there is no Terminology as Spice Databases in QS. Its a in-memory Datastore in spice where you can import Data from your sources like(S3, Athena etc) to serve low latency Visualizations. So for example if you have a scenario where you need a analysis which needs fast execution, needs to be used multiple times and need to join data from multiple datasets , then as a best practice u should all those datasets imported to spice engine . Infact this will be a cost efficient rather than querying a source directly which has cost implications of querying it. Refer this link - https://docs.aws.amazon.com/quicksight/latest/user/spice.html

Also the cost of Spice engine is charged per GB/Month and has no co relation with how many datasets you have in spice engine. So import datasets in spice diligently only for analysis in scenarios mentioned above(refer the link above)

Please refer pricing link -https://aws.amazon.com/quicksight/pricing/

Thanks

AWS
답변함 2년 전
-1

Hi, @ZeBron.

I understood that SPICE database = dataset.
You can calculate the capacity in the following way.

https://dev.classmethod.jp/articles/quicksight-spice-sizing/

The SPICE usage can be calculated from the field size and the number of columns.
The answer is that when you create your analyzes and dashboards it depends on the data structure as the cost will vary depending on how many unnecessary fields and rows are included.
The number of SPICE datasets by itself does not matter.

profile picture
전문가
iwasa
답변함 2년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠