page315
403
FROM snowflake.account_usage.query_history
WHERE warehouse_name IS NOT NULL
AND bytes_spilled_to_local_storage > 0
AND bytes_spilled_to_remote_storage > 0;
Guidance on resolving spills to disk and OOM is provided in Chapter 3. You can find
more information on spills to disk at
https://community.snowflake.com/s/article/
Performance-impact-from-local-and-remote-disk-spilling
.
Snowflake Support
In the event all of the previous does not identify a root cause for the issues encountered,
Snowflake Support is the first point of contact. During the writing of this book, I used
trial accounts and found Snowflake Support very responsive and helpful. I recommend
contacting Snowflake Support where required, even for trial accounts; you can find more
information at
https://www.snowflake.com/support/
. You can raise a support case by
following the guide at
https://community.snowflake.com/s/article/How-To-Submit-
a-Support-Case-in-Snowflake-Lodge
.
Depending upon the level of support provided to your organization, there may be
a sales engineer or performance expert dedicated to assisting you. The very best sales
engineers proactively monitor consumption and will highlight problematic queries for
your further investigation. I advise you to cultivate a good working relationship with your
sales engineer and, where available, your performance expert too.
Snowflake Feature Use Cases
If you have arrived at this section without developing a deep understanding of your
performance issue root cause, I recommend working through this chapter from the start.
I do not recommend blindly implementing any feature without a full understanding of
the potential impact.
In this chapter, you have examined many performance tuning tips to both reduce
costs and reduce query runtimes. I expect these tips to deliver impactful business
benefits, and I recommend both thorough investigation and testing before proceeding
further.
ChapTer 10
OpTimizing perfOrmanCe