On Fri, 2002-12-06 at 19:25, PcGoober wrote: > Overall it will act as a web/ejb applications, file/print and db server. > > We are a small company (< 100 peeps) so I don't expect the loads to be too > bad but I don't have any numbers to back me up so it is just a guess. The > only real unknown is if when we start using it to serve up our website data > but that is a little ways off and as long as a hardware upgrade isn't a > nightmare we should be ok. >
The first thing to do is add another HDD - get it running (software) RAID-1 to improve the odds of surviving a disk failure (and a small read performance improvement :-). I would add more RAM if you can. The Java stuff eats it, as can the DB if you want it to, and any file caching is good for performance and helps cushion the disk IO somewhat. SAP DB puts it's DB files under /var/opt/sapdb by default, and there will be other stuff going on in /var as well (print spool etc). It's probably a good idea to run that on a separate partition in case something goes wrong. The SAP DB manual has suggestions about disk layout, but your loads may not be high enough to warrant a separate disk per database volume. Also, I'm guessing it's a regular IDE system(?) and these seem to choke when given a whole lot of concurrent disk access to do. I guess time will tell... Just monitor it, and listen to the users, then get some stats going to figure out where the bottlenecks are. > To begin with the server will be running another MySQL db server with low > usage as well as other general purpose services such as samba, apache, > tomcat, etc. > > Thanks for the help. > > kev -- Richard Barrington <[EMAIL PROTECTED]> _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
