Difference between revisions of "SUNScholar/Install Ubuntu/S01"
| Line 17: | Line 17: | ||
===Partition Sizing=== | ===Partition Sizing=== | ||
The following partition scheme is reccomended. | The following partition scheme is reccomended. | ||
| − | {|class="wikitable" width=" | + | {|class="wikitable" width="95%" |
|- | |- | ||
| | | | ||
Revision as of 11:44, 8 August 2012
Step 1. Requirements
Software
We use the LTS versions of Ubuntu for our servers. For more information about the Ubuntu LTS server go to:
http://www.ubuntu.sun.ac.za/wiki/index.php/Enterprise_Server_Management
The server installation CD can be downloaded from:
ftp://ftp.sun.ac.za/iso-images/ubuntulinux/10.04/ubuntu-10.04.4-server-amd64.iso
Burn the above ISO image to a blank CD. Do not copy it as data, it MUST be burned as an ISO image !
If you have problems burning your own CD, then please ask your IT support people to help you.
Hardware
At the moment we use a DELL R710 server. With the following specifications:
- 2x Intel E5650 64 bit = 12 real CPU's and 24 virtual CPU's
- 12GB 1333Hz RAM
- 400GB RAID5 disk array using 10K RPM disks
- 4x 100MB Ethernet ports
Partition Sizing
The following partition scheme is reccomended.
|
/ |
ROOT partition, where all the system software is installed |
10GB Minimum - 20GB preferred |
|
n/a |
SWAP partition |
2x installed RAM |
|
/var |
VAR partition, where all the log files and database files are installed |
10GB Minimum - 20GB preferred. This depends on how big your database index files get. |
|
/home |
HOME partition, where all the DSpace software files and bitstreams are stored |
All the rest of the total disk capacity. |
|
All our tweaks and optimisations seem to be working. The load dropped when we started using "authbind" for Tomcat thereby eliminating the need for the Apache "mod_jk" module, which was creating extra processing overhead.
|
Looks like we have enough disk space in the /home partition for the next 3yrs at least, at our current rate of submissions. The /var partition which holds the database was reduced in size by tweaking the bitstream checker properties and then running a full database vacuum.
|
|
We have more than enough compute muscle.
|
Our memory usage stabilised when we stopped using the JSPUI. However after the upgrade to DSpace 1.8.2 and enabling discovery we are back to a memory intensive system.
|
PREVIOUS
NEXT
