Two Indys, one R5000 based system and an older R4400 based system

Indy R5000PC 150 MHz (Empress)


Sony power supply.
MAC Address: 08:00:69:09:AB:E2

  • CPU: MIPS R5000 Processor Chip Revision: 1.0
  • FPU: MIPS R5000 Floating Point Coprocessor Revision: 1.0
  • 1 150 MHZ IP22 Processor
  • Main memory size: 256 Mbytes
  • Instruction cache size: 32 Kbytes
  • Data cache size: 32 Kbytes
  • Integral SCSI controller 0: Version WD33C93B, revision D
  • Disk drive: unit 1 on SCSI controller 0 (unit 1)
  • On-board serial ports: 2
  • On-board bi-directional parallel port
  • Graphics board: Indy 8-bit
  • Integral Ethernet: ec0, version 1
  • Integral ISDN: Basic Rate Interface unit 0, revision 1.0
  • Iris Audio Processor: version A2 revision 4.1.0
  • Vino video: unit 0, revision 0, IndyCam not connected

The storage is based on SCSI2SD. This allows the usage of SD-Cards instead of 50-pin SCSI disks. It's slower than actually using a spinning disk because SCSI2SD is not a high performance solution. The SCSI2SD site states about 2.6 MB/s as the best achievable speed. The advantages lie within the lower heat and noise emissions.
Note: SCSI2SD (firmware v4.6) does not support SCSI SYNC. From time to time error messages complain about SYNC failures which can be ignored.
If you are curious, here is a diskperf run on this Indy with SCSI2SD:

Empress 1% diskperf -W -D -n SCSI2SD-Indy5000PC-150MHz -t10 -c100m testfile
#---------------------------------------------------------
# Disk Performance Test Results Generated By Diskperf V1.2
#
# Test name : SCSI2SD-Indy5000PC-150MHz
# Test date : Sat Mar 19 06:06:42 2016
# Test machine : IRIX Empress 6.5 01091820 IP22
# Test type : XFS data subvolume
# Test path : testfile
# Request sizes : min=4096 max=4194304
# Parameters : direct=1 time=10 scale=1.000 delay=0.000
# XFS file size : 104857600 bytes
#---------------------------------------------------------
# req_size fwd_wt fwd_rd bwd_wt bwd_rd rnd_wt rnd_rd
# (bytes) (MB/s) (MB/s) (MB/s) (MB/s) (MB/s) (MB/s)
#---------------------------------------------------------
4096 0.85 0.84 0.60 0.88 0.73 0.86
8192 1.10 0.98 0.96 1.01 0.54 1.00
16384 1.27 1.03 0.43 1.13 0.09 1.11
32768 1.18 1.18 0.79 1.18 0.17 1.17
65536 1.21 1.23 0.98 1.23 0.32 1.23
131072 1.25 1.20 1.08 1.26 0.55 1.25
262144 1.33 1.27 1.24 1.26 1.07 1.27
524288 1.23 1.15 1.24 1.28 1.14 1.21
1048576 1.08 1.28 1.31 1.21 1.29 1.28
2097152 1.22 1.28 1.23 1.28 1.38 1.28
4194304 1.45 1.21 1.24 1.28 1.44 1.25


Indy R4400SC 200 MHz (Grissom)


The R4400 system comes with a GR3-ZX “express” graphics board. Nidec power supply.
MAC Address: 08:00:69:08:DD:EE

  • CPU: MIPS R4400 Processor Chip Revision: 6.0
  • FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
  • 1 200 MHZ IP22 Processor
  • Main memory size: 256 Mbytes
  • Secondary unified instruction/data cache size: 1 Mbyte on Processor 0
  • Instruction cache size: 16 Kbytes
  • Data cache size: 16 Kbytes
  • Integral SCSI controller 0: Version WD33C93B, revision D
  • Disk drive: unit 1 on SCSI controller 0 (unit 1)
  • On-board serial ports: 2
  • On-board bi-directional parallel port
  • Graphics board: GR3-XZ
  • Integral Ethernet: ec0, version 1
  • Integral ISDN: Basic Rate Interface unit 0, revision 1.0
  • Iris Audio Processor: version A2 revision 4.1.0
  • Vino video: unit 0, revision 0, IndyCam not connected

This system is equipped with a SCSI2SD adapter and a SD-Card, too. Here are the diskperf numbers:

Grissom 1% diskperf -W -D -n SCSI2SD-Indy4400SC-200MHz -t10 -c100 testfile
#---------------------------------------------------------
# Disk Performance Test Results Generated By Diskperf V1.2
#
# Test name : SCSI2SD-Indy4400SC-200MHz
# Test date : Fri Mar 18 13:20:35 2016
# Test machine : IRIX Grissom 6.5 10070055 IP22
# Test type : XFS data subvolume
# Test path : testfile
# Request sizes : min=4096 max=4194304
# Parameters : direct=1 time=10 scale=1.000 delay=0.000
# XFS file size : 4194304 bytes
#---------------------------------------------------------
# req_size fwd_wt fwd_rd bwd_wt bwd_rd rnd_wt rnd_rd
# (bytes) (MB/s) (MB/s) (MB/s) (MB/s) (MB/s) (MB/s)
#---------------------------------------------------------
4096 0.64 0.72 0.63 0.72 0.59 0.71
8192 0.93 0.91 0.94 0.92 0.71 0.91
16384 1.16 1.06 0.43 1.06 0.40 1.06
32768 1.28 1.16 0.63 1.16 0.72 1.15
65536 1.37 1.21 1.06 1.20 0.98 1.21
131072 1.41 1.24 1.24 1.24 1.23 1.24
262144 1.44 1.25 1.36 1.25 1.38 1.25
524288 1.45 1.26 1.44 1.26 1.45 1.26
1048576 1.46 1.26 1.45 1.26 1.45 1.26
2097152 1.47 1.27 1.47 1.27 1.47 1.27
4194304 1.47 1.28 0.00 0.00 1.47 1.28


It looks like the better CPU of the R5000 based Indy leads to slighty better performance with small files. However it's still in a very low performance segment on both systems. But then, these systems are oldies by every standard. I have no explanation why the last two backward (bwd) read and write tests resulted in 0.00 MB/s.