firestorm
2007-01-30, 07:31
I'm on my fourth slimserver iteration now. I started off with a virtual pc running XP and windows shared folders. The virtual pc was running under ESX v2.2 dual P3 1Ghz and had 512Mb RAM dedicated to it. Disk space was a 5 x 250Gb raid 5 array with a Megalogic sata pcix controller. Performance was ok, though the networking performance was dire.
The 2nd version was similar, but using the excellent slimcd. The web interface was a litle snappier. I used this for a while, but decided the machine I was running it on, a dual proc HP, almost the size of a fridge was too power hungry, so I downsized it to a athlon 900, by that time I had found ClarkConnect which I liked and perservered with for 6 months or so which was the 3rd version.
Ultimately I found it removed me too far from the OS, but getting to the OS meant getting down and dirty with Linux. The issues I had were problems with permissions for sharing and slimserver, getting plugins to work etc.
I decided to simplify the setup and bought the following :
1) Asus P5BE Plus mb
2) Intel Core2duo 6300
3) 2 x 1Gb Corsair Value Select PC6400
4) 380W thermaltake silent psu
I already had
1) 5 x 250Gb Seagate Baracuda sata HD for data
2) 1 x 80Gb Seagate Baracuda sata HD for OS
I'm running SlimServer Version: 6.5.1 - 11064 - Windows Server 2003 - EN - cp1252
As you'd expect it runs very, very well, I don't have issues transcoding, scanning. The server does my non music fileserving too.
I bought a power meter a while back, the inline type with a lcd display. Go the following results :
1) HP Netserver LH3000 (dual P3 1Ghz, 4Gb ram) 360VA
2) AMD athlon 900, 1Gb ram 210VA
3) New dual core 6300, 2Gb ram 120VA
* HP server running 5 x sata, 5 x scsi
others 5xsata + 1 IDE or 6xsata
I feel a little more omfortable leaving these one most of the time. I'm trying to figure a good way of getting the server to switch off by itself.
I ideally something like:
1) No requests for files or music > 60 minutes switch off
2) Request for music or files switch on for 120 minutes min
The 2nd version was similar, but using the excellent slimcd. The web interface was a litle snappier. I used this for a while, but decided the machine I was running it on, a dual proc HP, almost the size of a fridge was too power hungry, so I downsized it to a athlon 900, by that time I had found ClarkConnect which I liked and perservered with for 6 months or so which was the 3rd version.
Ultimately I found it removed me too far from the OS, but getting to the OS meant getting down and dirty with Linux. The issues I had were problems with permissions for sharing and slimserver, getting plugins to work etc.
I decided to simplify the setup and bought the following :
1) Asus P5BE Plus mb
2) Intel Core2duo 6300
3) 2 x 1Gb Corsair Value Select PC6400
4) 380W thermaltake silent psu
I already had
1) 5 x 250Gb Seagate Baracuda sata HD for data
2) 1 x 80Gb Seagate Baracuda sata HD for OS
I'm running SlimServer Version: 6.5.1 - 11064 - Windows Server 2003 - EN - cp1252
As you'd expect it runs very, very well, I don't have issues transcoding, scanning. The server does my non music fileserving too.
I bought a power meter a while back, the inline type with a lcd display. Go the following results :
1) HP Netserver LH3000 (dual P3 1Ghz, 4Gb ram) 360VA
2) AMD athlon 900, 1Gb ram 210VA
3) New dual core 6300, 2Gb ram 120VA
* HP server running 5 x sata, 5 x scsi
others 5xsata + 1 IDE or 6xsata
I feel a little more omfortable leaving these one most of the time. I'm trying to figure a good way of getting the server to switch off by itself.
I ideally something like:
1) No requests for files or music > 60 minutes switch off
2) Request for music or files switch on for 120 minutes min