<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on</title><link>https://docs.protegrity.com/cloud-protect/4.0.0/docs/azure/snowflake/performance/</link><description>Recent content in Performance on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/cloud-protect/4.0.0/docs/azure/snowflake/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Function App Performance</title><link>https://docs.protegrity.com/cloud-protect/4.0.0/docs/azure/snowflake/performance/function_app/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/cloud-protect/4.0.0/docs/azure/snowflake/performance/function_app/</guid><description>&lt;h2 id="function-app-performance">Function App Performance&lt;/h2>
&lt;h3 id="overview">Overview&lt;/h3>
&lt;p>Azure Function apps offer different hosting plans that directly impact the performance, scalability, and cost of Cloud Protect deployments.
Understanding these plans and their characteristics is essential for optimizing your data protection operations.&lt;/p>
&lt;h3 id="azure-function-app-service-plans">Azure Function App Service Plans&lt;/h3>
&lt;p>Azure Functions provides several hosting options, each with different characteristics:&lt;/p>
&lt;h4 id="consumption-plan">Consumption Plan&lt;/h4>
&lt;p>The Consumption plan provides automatic scaling and charges only for compute resources used during function execution. While cost-effective for sporadic workloads, this plan has limitations:&lt;/p></description></item><item><title>Log Forwarder Performance</title><link>https://docs.protegrity.com/cloud-protect/4.0.0/docs/azure/snowflake/performance/log_forwarder/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/cloud-protect/4.0.0/docs/azure/snowflake/performance/log_forwarder/</guid><description>&lt;p>

 




	






 






 &lt;ol id="toc">&lt;/ol>
&lt;script>
 // JavaScript to generate the table of contents from H2 headings
 document.addEventListener("DOMContentLoaded", function () {
 //get all h2 headings within the 'main' element and generate a toc with links to them
 //excluding h2 heading 'Feedback' if it exists
 const toc = document.getElementById("toc");
 const headings = document.querySelectorAll("main h2");
 headings.forEach(heading => {
 if (heading.textContent === "Feedback") {
 return; // Skip the 'Feedback' heading
 }

 const li = document.createElement("li");
 const a = document.createElement("a");
 const id = heading.textContent.toLowerCase().replace(/\s+/g, '-');
 heading.id = id; // Set the id for the heading
 a.href = `#${id}`;
 a.textContent = heading.textContent;
 li.appendChild(a);
 toc.appendChild(li);
 });

 });
&lt;/script>





 




	






 






 &lt;p>

 




	






 






 &lt;h2 id="log-forwarder-performance">Log Forwarder Performance&lt;/h2>
&lt;p>Log forwarder architecture is optimized to minimize the amount of connections and reduce the overall network bandwidth required to send audit logs to ESA. This is achieved with batching and aggregation taking place on two levels.&lt;/p></description></item></channel></rss>