<?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 Re: Garbage Collection optimization in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/garbage-collection-optimization/m-p/21805#M14897</link>
    <description>&lt;P&gt;You can also tune the JVM's GC parameters directly, if you mean the pauses are too long. Set "spark.executor.extraJavaOptions", but it does require knowing a thing or two about how to tune for what performance goal.&lt;/P&gt;</description>
    <pubDate>Tue, 22 Jun 2021 16:06:59 GMT</pubDate>
    <dc:creator>sean_owen</dc:creator>
    <dc:date>2021-06-22T16:06:59Z</dc:date>
    <item>
      <title>Garbage Collection optimization</title>
      <link>https://community.databricks.com/t5/data-engineering/garbage-collection-optimization/m-p/21803#M14895</link>
      <description>&lt;P&gt;I have a case where  garbage collection is taking much time and I want to optimize it for better performance&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jun 2021 13:08:09 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/garbage-collection-optimization/m-p/21803#M14895</guid>
      <dc:creator>User16826994223</dc:creator>
      <dc:date>2021-06-22T13:08:09Z</dc:date>
    </item>
    <item>
      <title>Re: Garbage Collection optimization</title>
      <link>https://community.databricks.com/t5/data-engineering/garbage-collection-optimization/m-p/21804#M14896</link>
      <description>&lt;P&gt;You can use smaller instances with less ram than the VMs with higher ram, However there will be a trade  off   if there are lots of shuffle involve in the operation, because more small memory vms will increase the shuffling operation time &lt;/P&gt;</description>
      <pubDate>Tue, 22 Jun 2021 13:12:26 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/garbage-collection-optimization/m-p/21804#M14896</guid>
      <dc:creator>User16826994223</dc:creator>
      <dc:date>2021-06-22T13:12:26Z</dc:date>
    </item>
    <item>
      <title>Re: Garbage Collection optimization</title>
      <link>https://community.databricks.com/t5/data-engineering/garbage-collection-optimization/m-p/21805#M14897</link>
      <description>&lt;P&gt;You can also tune the JVM's GC parameters directly, if you mean the pauses are too long. Set "spark.executor.extraJavaOptions", but it does require knowing a thing or two about how to tune for what performance goal.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jun 2021 16:06:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/garbage-collection-optimization/m-p/21805#M14897</guid>
      <dc:creator>sean_owen</dc:creator>
      <dc:date>2021-06-22T16:06:59Z</dc:date>
    </item>
  </channel>
</rss>

