<?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: Performance Tuning wiht Applying Pseudo Windchill Cluster for CAD Workers and Replication File servers in Windchill</title>
    <link>https://community.ptc.com/t5/Windchill/Performance-Tuning-wiht-Applying-Pseudo-Windchill-Cluster-for/m-p/181914#M21608</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just to make sure everyone is away, there is no failover for Windchill background method servers. They die, windchill has to be restarted. All one big method server divided into smaller foregrounds and backgrounds.&lt;BR /&gt; &lt;BR /&gt; In Reply to Patrick Chin:&lt;/P&gt;&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;BR /&gt;&lt;P&gt;If you need to publish 10,000 jobs a day, and your users are getting affected by the 16 CAD workers cranking in the foreground method server, try applying a pseudo Windchill cluster and point your CAD workers andreplication fie serversto a slave. You don't need an expensive load balancer, the users will point to the other slave. That might help but you may have other IT infrasturcture issue out of your control that will cause performance issues. You can also have a https slave for external users.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;Patrick&lt;/P&gt;&lt;BR /&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Jun 2014 22:41:01 GMT</pubDate>
    <dc:creator>patrickchin2000</dc:creator>
    <dc:date>2014-06-04T22:41:01Z</dc:date>
    <item>
      <title>Performance Tuning wiht Applying Pseudo Windchill Cluster for CAD Workers and Replication File servers</title>
      <link>https://community.ptc.com/t5/Windchill/Performance-Tuning-wiht-Applying-Pseudo-Windchill-Cluster-for/m-p/181913#M21607</link>
      <description>If you need to publish 10,000 jobs a day, and your users are getting affected by the 16 CAD workers cranking in the foreground method server, try applying a pseudo Windchill cluster and point your CAD workers andreplication fie serversto a slave. You don't need an expensive load</description>
      <pubDate>Wed, 02 May 2018 13:39:08 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Performance-Tuning-wiht-Applying-Pseudo-Windchill-Cluster-for/m-p/181913#M21607</guid>
      <dc:creator>patrickchin2000</dc:creator>
      <dc:date>2018-05-02T13:39:08Z</dc:date>
    </item>
    <item>
      <title>RE: Performance Tuning wiht Applying Pseudo Windchill Cluster for CAD Workers and Replication File servers</title>
      <link>https://community.ptc.com/t5/Windchill/Performance-Tuning-wiht-Applying-Pseudo-Windchill-Cluster-for/m-p/181914#M21608</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just to make sure everyone is away, there is no failover for Windchill background method servers. They die, windchill has to be restarted. All one big method server divided into smaller foregrounds and backgrounds.&lt;BR /&gt; &lt;BR /&gt; In Reply to Patrick Chin:&lt;/P&gt;&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;BR /&gt;&lt;P&gt;If you need to publish 10,000 jobs a day, and your users are getting affected by the 16 CAD workers cranking in the foreground method server, try applying a pseudo Windchill cluster and point your CAD workers andreplication fie serversto a slave. You don't need an expensive load balancer, the users will point to the other slave. That might help but you may have other IT infrasturcture issue out of your control that will cause performance issues. You can also have a https slave for external users.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;Patrick&lt;/P&gt;&lt;BR /&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jun 2014 22:41:01 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Performance-Tuning-wiht-Applying-Pseudo-Windchill-Cluster-for/m-p/181914#M21608</guid>
      <dc:creator>patrickchin2000</dc:creator>
      <dc:date>2014-06-04T22:41:01Z</dc:date>
    </item>
  </channel>
</rss>

