Hi Krish I imagine you won't get very many replies to this, and this reply will not come with anything new either. I've written fairly extensively on The /Fallacy Minimum Hardware Requirements as well as on how out of date Open Text's own Minimum Hardware Requirements. I've also sized and scaled probably hundreds of different Content Server-based solutions and while I completely understand your request, it is almost impossible to meet it given the information you have provided.

Content Server is a very useful engine that can do many different things, 15 years ago or so it was quite accurate to suggest that Livelink (as it was known then) had an application footprint, that you could legitimately compare to Livelink-based solutions. But that was when Livelink was virtually the entire solution and the solution space was simply Document Management.

ECM is quite different, it isn't a single solution but many solutions rolled onto one engine and thus, in order to determine what sort of hardware footprint you need you first need to understand what solution(s) you are putting in place. Some are CPU intensive, some are I/O (network bandwidth) intensive, some are DB intensive, some are all three and some are simply lightweight all round.

There are dozens of high-level solutions, hundreds of distinct modules and literally thousands of individual functions all with transaction times that range from 10ms to 10,000ms ... it isn't possible to give an accurate recommendation without more business-oriented information.

If you can provide some more detail, I can probably get you further alone the path, but I firmly believe that the days where a single paper could describe an appropriate hardware environment for Content Server are over.