The server my mud is running on (which also runs this website) is spending way too much time at 100% CPU utilization. As is typical of java programs, the mud uses a lot of RAM. Lately it has been responding very slowly.
I’m going to try rebooting the server to see if that helps things, but I might not be able to run the mud until I can get the machine upgraded.
5 responses to “but I also know that you know what a weak-willed person I am”
What are the hardware specs, if you wouldn’t mind sharing?
elyograg@hedwig:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 5
model name : Pentium II (Deschutes)
stepping : 2
cpu MHz : 401.044
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr
bogomips : 790.52
elyograg@hedwig:~$ free
total used free shared buffers cached
Mem: 516408 503244 13164 0 58660 38388
-/+ buffers/cache: 406196 110212
Swap: 488248 37688 450560
elyograg@hedwig:~$ df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md1 915269 77215 789222 9% /
tmpfs 258204 16 258188 1% /dev/shm
/dev/md0 457568 14120 419036 4% /boot2
/dev/sda1 459143 15018 419628 4% /boot
/dev/md5 21483756 11894852 9588904 56% /home
/dev/sda5 3889892 1043184 2649112 29% /srcmnt
/dev/hda11 1053795 435230 562340 44% /srv
/dev/md4 915269 8496 857941 1% /tmp
/dev/md2 4805952 1366352 3195472 30% /usr
/dev/md6 9767120 1271072 8496048 14% /var
Nice – lotta memory and storage for that things day and age! That looks to be one pimped-out PII. 🙂
What’s the hard-drive setup? (I’m not familiar with using RAIDs under Linux (and is that SCSI too?).)
It has two 40MB IDE hard drives, one made by IBM, the other made by Western Digital.
hda: IBM-DTLA-305040, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 80418240 sectors (41174 MB) w/380KiB Cache, CHS=65535/16/63, UDMA(33)
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 p10 p11 >
hdc: WDC WD400BB-00AUA1, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: max request size: 128KiB
hdc: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(33)
/dev/ide/host0/bus1/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 p10 >
The motherboard BIOS is not capable of seeing a hard drive above 32GB, and hangs if it is asked to probe them. I installed a small SCSI disk that is used for booting and source-code storage. /usr/local/src is a symlink to /srcmnt. Once the system boots, Linux takes over and is able to access the IDE drives with no problem.
(scsi0:A:0): 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
Vendor: SEAGATE Model: ST34520W Rev: 1498
Type: Direct-Access ANSI SCSI revision: 02
scsi0:A:0:0: Tagged Queuing enabled. Depth 8
SCSI device sda: 8888924 512-byte hdwr sectors (4551 MB)
SCSI device sda: drive cache: write back
/dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 >
The two main drives are partitioned into 7 pieces that participate in RAID1. The first drive has one extra partition because it’s a little bit bigger than the other drive. I’ve got that mounted for extra storage if needed.
elyograg@hedwig:~$ cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 hda1[0] hdc1[1]
488256 blocks [2/2] [UU]
md2 : active raid1 hda6[0] hdc6[1]
4882624 blocks [2/2] [UU]
md4 : active raid1 hda8[0] hdc8[1]
976640 blocks [2/2] [UU]
md5 : active raid1 hda9[0] hdc9[1]
21484416 blocks [2/2] [UU]
md6 : active raid1 hda10[0] hdc10[1]
9767424 blocks [2/2] [UU]
md1 : active raid1 hda5[0] hdc5[1]
976640 blocks [2/2] [UU]
md3 : active raid1 hda7[0] hdc7[1]
488256 blocks [2/2] [UU]
Wow, thanks much for the hella-details – it\’s always educational to see how the experts do things. With drives getting as huge and un-backup-able as they are, it\’s high-time I set up a RAID on my own server.