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)
Web Server Set up and Performance Issues
Jamik
Product: TeamSite 6.1
Server: Windows Server 2003
Lately we've been running into performance issues with TeamSite. Actually we've had performance issues since the start of using 6.1 but they've just gotten worse over time as we've added more users. So my question what have other people done to help improve TeamSite performance. I've done some searching in the TS manuals and here on the forums and haven't found anything that would help in our situation. Has anyone done gzip compression or what type of performance enhancements would you suggest we do to help make TeamSite a more bareable system to use especially for our European users?
Find more posts tagged with
Comments
nipper
First with the amount of information you have given, it is impossible to answer your question.
Even with complete information, getting a significant amount of help from this forum will be unlikely.
Performance issues are an iterative process, find a bottleneck, improve it.
You would be best off by getting a consultant (from Interwoven or a very good independent) for a week
to evaluate the systems and make recommendations.
That being said. If you want to try to fix it yourself, start characterizing the issues. First take the
network out of it.
Run some tests, on a system local to the sever (use traceroute and ping to see how long transmission
takes). What are users trying to do ? How long does it take ? Try with an unloade system and with a
loaded system.
Jamik
I could've sworn i posted a response yesterday to this. Anyway, my questions was more directed towards wondering if anyone else has had performance issues and what they did to improve performance. Obviously, I'm not expecting to have my performance issues solved from these forums, but it could possibly give me some ideas to pursue in tracking down items that may be commonly known as performance lookouts. So if anyone has any performance stories I'd like to hear them in the hopes it might give me a starting point to look. I already know that it's not the network and had to do with the TeamSite box itself. I've people complain about poor performance with CC-Std UI and that's what all our users are using and doing any type of action in the CC-Std can get slow at times. So I suspect it's CC-Std that's the culprit, but we don't want our users using CC-Pro because they are not "power-users".
Also I'm curious if anyone has set up gzip compression for teamsite since this would help out our European users if we could turn compression on.
Adam Stoller
Also I'm curious if anyone has set up gzip compression for teamsite since this would help out our European users if we could turn compression on.
Where would you be expecting to set up gzip compression? For what operations?
Back before 5.5.2 there was a server configuration option for allowing compression of files in the backing store - it was removed in 5.5.2 because it was actually hurting performance more than helping it didn't really help disk space utilization that much either.
I imagine your European users are having problems with network latency between their location and the location of the TS server. There are two thoughts that come to mind:
The last item is something that I believe Interwoven and several of their global customers have played with a number of times, but I don't know if anyone ever came up with a definitive and reliable way to do it.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
Jamik
well, i'd be setting up gzip compression for the front end web services of TeamSite. from what i've read we'd have to set up a web server to be the TeamSite front end so that we could get gzip compression even installed since OOB TeamSite uses tomcat for it's webserver and tomcat doesn't do gzip compression. i saw they had an example of setting up IIS to be the web server for teamsite and that's probably the route we'd take since our windows web servers typically run IIS here.
We've done gzip compression for our portal server and that greatly improved end user experience so we thought that might help in our TeamSite side of things too.
Adam Stoller
I suggest you open up a case with Support on this - as this is something that you will probably need some assistance with and going through support, potentially to engineering, will be your best bet -- and at the same time you would be developing a feature request that might prove useful for other customers.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
bencollins
We had performance issues switching from 5.5.2 to 6.x too, especially for remote users. We did some performance checks and found that there was loads and loads of traffic on the network - caused by the fancy new GUI. Watch the status bar as you open a DCR and you'll see that loads of "items" are being downloaded each time.
There is a patch you can apply to TeamSite to apply some caching to the graphic and js/css code elements, and this has a massive impact on the performance.
If you have a support login the details are at:
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=53439
I hope this helps!
Ben
Migrateduser
Some simple solutions.
Change the Show:ALL to Show:10. Our users were complaining about the time it took for the first page to display on login in CCSTD and having them change this made a world of difference.
Secondly, are you deleting any editions. Deleting editions takes a heavy toll on the server, it especially cripples CCSTD. CCPRO seems to be able to perform fine.
How about an indication of how many documents you have, backing store size, branches, workareas, etc.
