OnDemand Server Sizing help for Linux system

[aro_oha]

We need to configure a CMOD system to run on Linux.  It's a sizeable requirement with the system having to satisfy a number of CMOD queries/retrievals per second at peak times.  We need to size this system;  that is decide on how many hardware processors, which processors and how much memory is required to give satisfactory fast response for the users.

Can anyone kindly assist us with sizing advice, rules of thumb, tools, spreadsheets, etc...?   

Many thanks in advance.  Olivier Hayot / Chris Corfield

[Justin Derrick]

IBM has a CMOD server sizing tool, but I'm not sure if they make it available to customers / partners.

If this is a migration, your best bet is to collect as much information about the number in inquiries/queries and retrievals as you can -- both in terms of totals per day/week/month, and peaks per hour / minute / second.

Post installation, let me know if you'd like some CMOD performance tuning services.  I have a complete set of reporting tools that provide a comprehensive view of utilization.

-JD.

[jsquizz]

We need to configure a CMOD system to run on Linux.  It's a sizeable requirement with the system having to satisfy a number of CMOD queries/retrievals per second at peak times.  We need to size this system;  that is decide on how many hardware processors, which processors and how much memory is required to give satisfactory fast response for the users.

Can anyone kindly assist us with sizing advice, rules of thumb, tools, spreadsheets, etc...?   

Many thanks in advance.  Olivier Hayot / Chris Corfield

This may or may not be helpful.

https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E877A7C04AB511E5BB33E7199C786195

Check the "Hardware" Tab

[Justin Derrick]

Well, those are the minimum recommendations, probably not suitable for production use.

-JD.

[Norbert Novotny]

We need to configure a CMOD system to run on Linux.  It's a sizeable requirement with the system having to satisfy a number of CMOD queries/retrievals per second at peak times.  We need to size this system;  that is decide on how many hardware processors, which processors and how much memory is required to give satisfactory fast response for the users.

One aspect to take in consideration, what do you call a "CMOD System":

• arssockd + arsload + DB2 + TSM(with DB2)
• arssockd + arsload + DB2 & SM is external e.g. different system aka cloud object store or remote TSM
• arssockd + arsload & DB2 or Oracle & SM remote
• arssockd & arsload on different system e.g. via ODWEK (though this is very unusual)

Also need to consider any other Services you may wish to run on the same box, such WAS/ICN, SAMBA (server and/or client), NFSd, sshd

Another question, how is the storage attached to the system, SAN, NAS or direct attached

As a rule of thumb I would say CMOD system is more IO intensive (Network & Disk)  rather than CPU, but someone could argue that point. I am assuming moderate balanced ratio between need to compress and pre-compressed, as well as more searches than actual retrievals.

Well, here is my 5¢ 
N.