nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Teamsite,OpenDeploy and Livesite Requirements

Luis David Moreno

Hello,

I'm new in the forum and I've been searching this information around with not success, I'm new also in Teamsite Technology and i would like to ask you for help based in your experience.

I've read in the manuals that a Teamsite server needs a minimum of 3 GHz dual core CPU and 4 Gb of RAM.

I would like to ask for you recommendation for a Teamsite server running Teamsite 7.3.1 with OpenDeploy and LiveSite.

What is the max amount of used RAM with Widnows server 2008 Enterprise
Recomended CPU speed and cores.
other hardware requirements or recomendations.

The number of users is variable with a maximum of 30 simultaneous. Deploying content from 3 different Content Stores.

Let me know if there is any other required information.

Find more posts tagged with

Comments

Rick Poulin

What is the max amount of used RAM with Widnows server 2008 Enterprise
Recomended CPU speed and cores.
other hardware requirements or recomendations.

The number of users is variable with a maximum of 30 simultaneous. Deploying content from 3 different Content Stores.

There is no maximum amount of RAM in 2k8 (well, there is, but your hardware and general availability of such chips will limit you before the OS does).

3GHz dualcore CPU is a good place to start and I'd consider that a minimum. 2GHZ quadcore would be better. Your wallet's the limit. You might want to allocate more RAM though (8GB) for a production install, just because most enterprises tend to have a bunch of other **** running on the server, like backups and monitoring and virus scan and whatnot.

Do you have a requirement for 3 content stores? That makes me think you're upgrading from a previous install, in which case you should have a pretty good idea what specs you're going to need. 7.x isn't that much more resource intensive than 6.x (it is slightly more, because of JBoss and additional products like LSCSAuth).

Luis David Moreno

Thanks for your reply rpoulin, and yes; this is more like an upgrade, we are looking to update from 6.7.2 to 7.3.1 and we are looking for the correct specs to have in our server concerning CPU and RAM, we currently have 32 GB in RAM and a quad core CPU @2.66Ghz, we are experiencing performance issues in the server and we like to know if that was because of the hardware, and if upgrading could decrease more the performance.

We noticed a lot of hard-faults in the system, we also know that this are not really fails or errors, but in a large number it can decrease overall performance.

OpenDeply and LiveSite resource consumption can be discarded or is something that we have to take in count? They are also hosted in the same server.

Thanks in advance for your responses!

RunReport.png

HowToChangeTheDefaultBrowserInOpenSourceBIRT.png

WorkspaceLocation.png

WorkspaceLogFile(ExtensionsHidden).png

WorkspaceLogFile.png

nipper

OpenDeply and LiveSite resource consumption can be discarded or is something that we have to take in count? They are also hosted in the same server.

OpenDeploy Base and Admin should be small in usage. Do not worry about those. The only LS app you should have is LSCS Authoring console. The others should be on the web/app servers. Is search installed on this computer or on another ? FYI, for 7.3.1 search will be installed on the TS server, because IDOL is used for LSCS Authoring.

It certainly sounds like your hardware specs are very good.

How many active users do you have ?

Bowker

we have 3BS and about 200-250 active users. We have a quad core with 12gb of RAM running on MS 2008 Enterprise Server. We found that 8gb just wasn't enough and the server kept having all sorts of issues including crashing and hanging. We went to 12gb and things are a lot better.
You Unix guys will love this.... We try to reboot once per month just to clean things up. The server tends to eat memory as time goes along. If I didn't have other fish to fry, I would ask for 16gb.

My motto is: More memory is always a good thing.

FanTom

You may have to look at your java configuration on the OS. On Solaris, the Java parameters will have to be in certain order. Check with Autonomy support on that order. I can send you an email exactly on what we found out and changed as fas as OS parameter is concerned.
Also setting up appropriate logging and during your development, organizing logs will also help your capacity/sizing.

Adam Stoller

OpenDeploy Base and Admin should be small in usage. Do not worry about those. ...

The one caveat I would offer with regard to the above is to check the size (lines, bytes, whatever) of your odnodes.xml file. There was a bug in OpenDeploy where it re-read the odnodes.xml file every time a deployment occurred (it's only supposed to do it when requested with a serverreset or a restart of the services as a whole) - and to make matters worse, if your odnodes.xml file is significantly large (*) the memory used to read the file doesn't get freed up correctly and the process starts using more and more memory with each deployment.

(* The case where we found this had a 6 Mb, 200,000 line odnodes.xml file - obviously pretty extreme, but ...)

I believe this bug was officially fixed in 7.3.1 but it's worth verifying the growth pattern of the OpenDeploy service over the course of N-deployments to make sure it's not "leaking".