Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
OD 5.6.0 Performance?
System
We recently upgraded to OD 5.6.0 (plus SP1 plus patches) on both our base and receiver servers and we are seeing performance problems transferring content from our base TeamSite server (on Win2K) to our intranet web server (RedHat Linux).
Our intranet site has about 2.5GB of content and prior to the upgrade (we were running 5.5.1) the initial deploy ran in around 5-6 hours and updates were taking anything upto 30 minutes. So far under 5.6.0 we've not managed to complete either a successful update or a fresh full deploy to a test directory. On the latter, I triggered a deploy yesterday and it's still running some 19 hours later, having so far transferred around 610MB.
It's got to the point where we are considering "downgrading" back to our 5.5.1 setup.
Are there any performance tweaks that we should be applying to either server config? I've looked at the documentation regarding file transfer buffers but it's not clear what the effect will be of increasing (or decreasing) this value.
Any hints, tips or answers will be most gratefully received - thanks.
Find more posts tagged with
Comments
Adam Stoller
Please contact Interwoven Support to work with them in replicating the situation. 5.6 should, if anything, be faster than 5.5.1 within the same environment pushing out the same data. If there is indeed a problem that is causing 5.6 to perform slower we'd like to be able to replicate it in-house so that we can diagnose and fix the issue. If it turns out to be something in your environment that is causing it to behave slower, we'd like to be able to help diagnose the issue so that you can fix the environment.
All of that is a lot easier to do via Support.
--fish
(Interwoven Senior Technical Consultant)
nipper
We noticed the same thing, our is in the case of a date_different deployment do_deletes = no, It is most noticable from our connfig branch to $iw-home
What the log keeps saying is ->
removing $iw-home/bin/iwserver SKIPPED
removing $..................................... SKIPPED
So it seems to be doing a great deal more checking that it does not need to do. Support told us "this was a bug fix"
Andy
Example.ssd
Migrateduser
could you try this...
turn off eventReporting
<eventReporting enabled="no" ... />
and
set the dnr infostream to log
<dnrProperties ... infoStreamFormat="log" ... />
I think more accurate state info needed to be collected
when performing eventReporting and manifest generation.
When you say 2.5G of content,
how many files is this?