<?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 We too observed the same… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Slowness-in-debug-mode-environment-post-upgrade-of-BP-to-version/m-p/74446#M27051</link>
    <description>We&amp;nbsp;too observed the same behavior after upgrading to 6.2.&amp;nbsp; Reverted BP to earlier version due to these performance issues. Please keep this post updated if any remedies received.</description>
    <pubDate>Mon, 04 Jun 2018 23:41:00 GMT</pubDate>
    <dc:creator>Prabhakara_Kuma</dc:creator>
    <dc:date>2018-06-04T23:41:00Z</dc:date>
    <item>
      <title>Slowness in debug mode/environment post upgrade of BP to version 6</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Slowness-in-debug-mode-environment-post-upgrade-of-BP-to-version/m-p/74444#M27049</link>
      <description>Hi All,

We are observing&amp;nbsp;slowness in overall BP environment version 6, especially at studio &amp;amp; running processes&amp;nbsp; , finally at fewer&amp;nbsp;places in processes it needed to add sleep times to make it work as it was working with earlier versions of BP .

Major issue that is seen while debugging&amp;nbsp;the&amp;nbsp;process , found that yellow highlight that is being shown at action is running behind &amp;nbsp;.

Observed that printing of actions logs and highlighting that particular action is not in sync in studio.

Not sure if anyone is facing the slowness issues after version upgrade to 6&amp;nbsp;.

&amp;nbsp;

Thanks,

Sandeep Kutwal&amp;nbsp;</description>
      <pubDate>Fri, 27 Apr 2018 11:20:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Slowness-in-debug-mode-environment-post-upgrade-of-BP-to-version/m-p/74444#M27049</guid>
      <dc:creator>SandeepKutwal</dc:creator>
      <dc:date>2018-04-27T11:20:00Z</dc:date>
    </item>
    <item>
      <title>I recommend raising your…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Slowness-in-debug-mode-environment-post-upgrade-of-BP-to-version/m-p/74445#M27050</link>
      <description>I recommend raising your issue with the support team if you have not done so already - there should be no studio performance issue between 5 and 6.&amp;nbsp; Has anything else changed in your environment (such as a move from 32 to 64 bit etc..)
On a side note, I would not expect you to have had to amend all your wait stage timeouts.&amp;nbsp; If you were following best practices all your intelligent timeouts should already have been set to extra large numbers (I usually use 120 seconds).&amp;nbsp; This will not slow down your solution because as soon as an element is found the flow will continue, but it will make it more robust.</description>
      <pubDate>Tue, 01 May 2018 17:12:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Slowness-in-debug-mode-environment-post-upgrade-of-BP-to-version/m-p/74445#M27050</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2018-05-01T17:12:00Z</dc:date>
    </item>
    <item>
      <title>We too observed the same…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Slowness-in-debug-mode-environment-post-upgrade-of-BP-to-version/m-p/74446#M27051</link>
      <description>We&amp;nbsp;too observed the same behavior after upgrading to 6.2.&amp;nbsp; Reverted BP to earlier version due to these performance issues. Please keep this post updated if any remedies received.</description>
      <pubDate>Mon, 04 Jun 2018 23:41:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Slowness-in-debug-mode-environment-post-upgrade-of-BP-to-version/m-p/74446#M27051</guid>
      <dc:creator>Prabhakara_Kuma</dc:creator>
      <dc:date>2018-06-04T23:41:00Z</dc:date>
    </item>
  </channel>
</rss>

