tag:help-archives.hannonhill.com,2010-02-09:/discussions/installation/6707-after-upgrade-to-7142-slow-performanceCascade CMS: Discussion 2015-12-02T14:41:32Ztag:help-archives.hannonhill.com,2010-02-09:Comment/384002042015-11-06T19:01:17Z2015-11-06T19:01:17ZAfter upgrade to 7.14.2 , slow performance<div><p>Hey there,</p>
<p>If the dev server has 6GB of RAM total, I would definitely scale
down your allocation to Cascade to perhaps 3GB. When you have a
moment, try modifying the JAVA_OPTS line in your cascade.sh file
and change:<br></p>
<pre>
<code>-Xmx6192M</code>
</pre>
to this:<br>
<pre>
<code>-Xms3G -Xmx3G</code>
</pre>
Then, restart Cascade.
<p>The next thing I would recommend checking would be to see when
your scheduled link checker may be running. To do this, go to
System Menu -> Preferences -> General and look at the
Scheduled Link Checker Configuration. If this is currently
configured to run daily, I would recommend changing it to run
weekly - perhaps very early on Saturday or Sunday mornings.</p>
<p>If you don't see any improvement after taking these steps, go
ahead and zip up your <em>cascade.log</em> file from the past
couple of days and I'll be happy to look over them to see if I
notice any glaring problems.</p>
<p>Thanks!</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/384002042015-11-17T23:19:54Z2015-11-17T23:19:54ZAfter upgrade to 7.14.2 , slow performance<div><p>Hi Tim,</p>
<p>Thanks for you help. I believe that the problem was actually was
the Link Checker. We have several websites in our Cascade Server
instance. Most are very small, but one has 20,000 pages ( created
and updated using Cascade's web services ).</p>
<p>That site with 20K pages, seems to have been the problem. Once
the Link Checker was turned off for that site only, the slow
performance disappeared.</p>
<p>Of course we would have liked to use the link checker, but we
can live without it . For your reference, this is the error message
we saw in the logs :</p>
<p>2015-11-06 09:00:51,963 WARN [BrokenLinkReportServiceImpl] :
Broken link report generation took longer than 6 hours to complete.
Consider disabling link reporting for some Sites. Also consider
changing the link report schedule from daily to weekly as this will
allow the report to run longer before being interrupted. Broken
Link Report may not have been generated for some Sites due the
alotted amount of time being depleted before those Sites could be
processed.</p></div>jperreaulttag:help-archives.hannonhill.com,2010-02-09:Comment/384002042015-11-18T14:43:03Z2015-11-18T14:43:03ZAfter upgrade to 7.14.2 , slow performance<div><p>Thanks for the update! One other thing you can consider (which
may or may not help, it's tough to tell) would be to increase the
number of CPUs and/or the speed of the processors. Obviously this
will be difficult on a physical machine, but should be pretty easy
to experiment with if you're running on VMs. That, in combination
with the memory increase I suggested above might help a bit.</p>
<p>Let me know if you need anything else!</p></div>Tim