Author |
Message |
granted
Joined: Sep 13, 2006 Posts: 1 Location: earth
|
Posted: Sun Dec 16, 2007 8:48 am Post subject:
Quad Core - On Topic Answer |
 |
|
I recently upgraded my rig to an Intel Q6600 from a P4 3.0.
It's awesome.
I'm running the q6600 on an Asus Commando motherboard.
I got the Commando because of my legacy PCI hardware: EMU 1820M, 2 UAD PCI and 1 Poco PCI.
The Commando is one of the few boards with 4 PCI slots.
The upgrade was easy. I just swapped out the boards and and had the new driver CD ready. Because the previous board was a 865 based chipset and the Commando is a 965 based chipset the swap upgrade was very smooth.
What do you get with a Q6600? VSTi's for days and days. Have fun trying to max your CPU out. I haven't been able to yet.
I run Cubase Studio 4.1.1 and Live 6 and 7. I also use the Komplete 5 and Kore 2.
Everything works great ... well you know, as great as software can work :wink:
Btw some people may be scratching their heads about my upgrade. "you mean you didn't backup, wipe your drives and reinstall everything from scratch???" That's right I did not. :D
I always do this first, if my system works then I keep it. Please let it be known that I keep daily,weekly,monthly backups so my fear factor is zero.
Also my day job is a computer tech. so again my tech worries are few.
If you've ever had to reinstall Komplete 4 then upgrade to Komplete 5 then ... not to mention the Live 7 Suite install then you'll know why I go for the "plug and pray" before the "wipe and loose a day".
Get a Quad Core! If you use VSTi's then it is a no brainer. IT will save you time and let you stop freezing tracks. Massive in HQ mode? no problem.
Now my only problem is my P4 D 3.2 that sits next to the Quad is getting jealous. I've tried to explain to my P4 D that she is for email, web and games but she ain't having it. |
|
Back to top
|
|
 |
Jason

Joined: Aug 12, 2004 Posts: 466 Location: Los Angeles, CA. USA
|
Posted: Wed Dec 19, 2007 12:00 am Post subject:
|
 |
|
Welcome to the Forum!
Sounds like a nice upgrade.
However I must ask, what information do you have regarding optimization with your VST's and quad-cores?
How do you know they aren't all running on 1 core?
I will contact NI to confirm that the CPU load is distributed etc.
Anyway, nice system and keep us posted!
Thanks |
|
Back to top
|
|
 |
BobTheDog

Joined: Feb 28, 2005 Posts: 4044 Location: England
Audio files: 32
G2 patch files: 15
|
Posted: Thu Dec 20, 2007 9:34 am Post subject:
|
 |
|
All NI plugins are single threaded apart from Kontakt. |
|
Back to top
|
|
 |
jksuperstar

Joined: Aug 20, 2004 Posts: 2503 Location: Denver
Audio files: 1
G2 patch files: 18
|
Posted: Thu Dec 20, 2007 2:46 pm Post subject:
|
 |
|
The plugin might be single threaded, but then you can run 3 or 4 plugins at near 100% CPU  |
|
Back to top
|
|
 |
BobTheDog

Joined: Feb 28, 2005 Posts: 4044 Location: England
Audio files: 32
G2 patch files: 15
|
Posted: Thu Dec 20, 2007 2:57 pm Post subject:
|
 |
|
Thats true to some extent as long as you add extra latency.
Daws at low latency with multi-processor/core machines still struggle.
Cubase 4 is a great example of a poorly written multi-processor audio engine I get better performance by turning multi-processor support off on my MacPro!
Logic fairs a bit better but on my 2 processor 4 core Mac pro still pegs out at around 250% using a 256 buffer.
Quad core chips may perform slightly better than this as the secondary cache is shareable by all four cores.
Don't get me wrong I am all for multi-processor core machines (My main work machine has 48 processors) but actual performance for each vst will probably be slightly worse, so running massive in HQ mode may actually perform worse on a multi-core machine.
Cheers
Andy |
|
Back to top
|
|
 |
Kassen
Janitor


Joined: Jul 06, 2004 Posts: 7678 Location: The Hague, NL
G2 patch files: 3
|
Posted: Thu Dec 20, 2007 7:59 pm Post subject:
|
 |
|
48!!!? what kind of architecture is that and can I ask what you run on it? _________________ Kassen |
|
Back to top
|
|
 |
BobTheDog

Joined: Feb 28, 2005 Posts: 4044 Location: England
Audio files: 32
G2 patch files: 15
|
Posted: Thu Dec 20, 2007 10:56 pm Post subject:
|
 |
|
Hi,
Its an SGI Origin 3000 running Irix:
http://www.sgi.com/products/remarketed/origin3000/overview.html
For the geeks here is the output from hinv:
Processor 0: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 1: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 2: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 3: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 4: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 5: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 6: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 7: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 8: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 9: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 10: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 11: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 12: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 13: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 14: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 15: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 16: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 17: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 18: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 19: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 20: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 21: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 22: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 23: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Processor 24: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 25: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 26: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 27: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 28: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 29: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 30: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 31: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 32: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 33: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 34: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 35: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 36: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 37: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 38: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 39: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 40: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 41: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 42: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 43: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 44: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 45: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 46: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Processor 47: 500 MHZ IP35
CPU: MIPS R14000 Processor Chip Revision: 1.4
FPU: MIPS R14010 Floating Point Chip Revision: 1.4
Main memory size: 48640 Mbytes
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
Secondary unified instruction/data cache size: 8 Mbytes
Integral SCSI controller 21: Version Fibre Channel QL2310
Fabric RAID controller: node 200500a0b811926c port 1 on SCSI controller 21
Fabric RAID lun: node 200500a0b811926c port 1 lun 0 on SCSI controller 21 (primary path)
Fabric RAID lun: node 200500a0b811926c port 1 lun 2 on SCSI controller 21 (alternate path)
Fabric RAID lun: node 200500a0b811926c port 1 lun 4 on SCSI controller 21 (primary path)
Fabric RAID lun: node 200500a0b811926c port 1 lun 6 on SCSI controller 21 (alternate path)
Fabric RAID controller: node 200500a0b811916a port 1 on SCSI controller 21
Fabric RAID lun: node 200500a0b811916a port 1 lun 0 on SCSI controller 21 (primary path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 2 on SCSI controller 21 (alternate path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 4 on SCSI controller 21 (primary path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 6 on SCSI controller 21 (alternate path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 8 on SCSI controller 21 (primary path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 10 on SCSI controller 21 (alternate path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 12 on SCSI controller 21
Fabric RAID lun: node 200500a0b811916a port 1 lun 13 on SCSI controller 21 (primary path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 15 on SCSI controller 21 (alternate path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 17 on SCSI controller 21 (primary path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 19 on SCSI controller 21 (alternate path)
Integral SCSI controller 11: Version Fibre Channel QL2310
Fabric RAID controller: node 200500a0b811926c port 1 on SCSI controller 11
Fabric RAID lun: node 200500a0b811926c port 1 lun 0 on SCSI controller 11 (alternate path)
Fabric RAID lun: node 200500a0b811926c port 1 lun 2 on SCSI controller 11 (primary path)
Fabric RAID lun: node 200500a0b811926c port 1 lun 4 on SCSI controller 11 (alternate path)
Fabric RAID lun: node 200500a0b811926c port 1 lun 6 on SCSI controller 11 (primary path)
Fabric RAID controller: node 200500a0b811916a port 1 on SCSI controller 11
Fabric RAID lun: node 200500a0b811916a port 1 lun 0 on SCSI controller 11 (alternate path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 2 on SCSI controller 11 (primary path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 4 on SCSI controller 11 (alternate path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 6 on SCSI controller 11 (primary path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 8 on SCSI controller 11 (alternate path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 10 on SCSI controller 11 (primary path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 12 on SCSI controller 11
Fabric RAID lun: node 200500a0b811916a port 1 lun 13 on SCSI controller 11 (alternate path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 15 on SCSI controller 11 (primary path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 17 on SCSI controller 11 (alternate path)
Fabric RAID lun: node 200500a0b811916a port 1 lun 19 on SCSI controller 11 (primary path)
Integral SCSI controller 6: Version Fibre Channel QL2310
Integral SCSI controller 14: Version Fibre Channel QL2310
Fabric RAID controller: node 200300a0b80f134d port 1 on SCSI controller 14
Fabric RAID lun: node 200300a0b80f134d port 1 lun 1 on SCSI controller 14 (alternate path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 3 on SCSI controller 14 (alternate path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 5 on SCSI controller 14 (alternate path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 7 on SCSI controller 14 (alternate path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 9 on SCSI controller 14 (alternate path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 11 on SCSI controller 14 (alternate path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 13 on SCSI controller 14 (alternate path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 15 on SCSI controller 14 (alternate path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 17 on SCSI controller 14 (alternate path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 19 on SCSI controller 14 (alternate path)
Integral SCSI controller 24: Version Fibre Channel QL2342 Port 1
Integral SCSI controller 0: Version Fibre Channel QL2200A
Disk drive: unit 1 on SCSI controller 0
Disk drive: unit 2 on SCSI controller 0
Integral SCSI controller 5: Version IEEE1394 SBP2
IEEE1394 CDROM: node 1010031001c44f port 0 on SCSI controller 5
Integral SCSI controller 15: Version Fibre Channel QL2310
Fabric Tape: node 500104f000901d9a port 1 on SCSI controller 15: Async Personality Device
Fabric Tape: node 500104f000901dca port 1 on SCSI controller 15: Async Personality Device
Fabric Tape: node 500104f000901e2a port 1 on SCSI controller 15: Async Personality Device
Fabric Tape: node 500104f0008a1ddc port 2 on SCSI controller 15: Async Personality Device
Integral SCSI controller 22: Version Fibre Channel QL2310
Fabric RAID controller: node 200200a0b80f134d port 1 on SCSI controller 22
Fabric RAID lun: node 200200a0b80f134d port 1 lun 0 on SCSI controller 22 (alternate path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 2 on SCSI controller 22 (alternate path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 4 on SCSI controller 22 (alternate path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 6 on SCSI controller 22 (alternate path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 8 on SCSI controller 22
Fabric RAID lun: node 200200a0b80f134d port 1 lun 10 on SCSI controller 22 (alternate path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 12 on SCSI controller 22 (alternate path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 14 on SCSI controller 22 (alternate path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 16 on SCSI controller 22 (alternate path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 18 on SCSI controller 22 (alternate path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 20 on SCSI controller 22 (alternate path)
Integral SCSI controller 7: Version Fibre Channel QL2342 Port 1
Fabric Tape: node 500104f000901d91 port 1 on SCSI controller 7: Async Personality Device
Fabric Tape: node 500104f000901df1 port 1 on SCSI controller 7: Async Personality Device
Fabric Tape: node 500104f0008a1e0c port 1 on SCSI controller 7: Async Personality Device
Integral SCSI controller 12: Version Fibre Channel QL2342 Port 1
Fabric RAID controller: node 200300a0b80f134d port 1 on SCSI controller 12
Fabric RAID lun: node 200300a0b80f134d port 1 lun 1 on SCSI controller 12 (primary path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 3 on SCSI controller 12 (primary path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 5 on SCSI controller 12 (primary path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 7 on SCSI controller 12 (primary path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 9 on SCSI controller 12 (primary path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 11 on SCSI controller 12 (primary path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 13 on SCSI controller 12 (primary path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 15 on SCSI controller 12 (primary path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 17 on SCSI controller 12 (primary path)
Fabric RAID lun: node 200300a0b80f134d port 1 lun 19 on SCSI controller 12 (primary path)
Integral SCSI controller 16: Version Fibre Channel QL2310
Fabric RAID controller: node 200200a0b80f134d port 1 on SCSI controller 16
Fabric RAID lun: node 200200a0b80f134d port 1 lun 0 on SCSI controller 16 (primary path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 2 on SCSI controller 16 (primary path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 4 on SCSI controller 16 (primary path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 6 on SCSI controller 16 (primary path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 8 on SCSI controller 16
Fabric RAID lun: node 200200a0b80f134d port 1 lun 10 on SCSI controller 16 (primary path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 12 on SCSI controller 16 (primary path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 14 on SCSI controller 16 (primary path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 16 on SCSI controller 16 (primary path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 18 on SCSI controller 16 (primary path)
Fabric RAID lun: node 200200a0b80f134d port 1 lun 20 on SCSI controller 16 (primary path)
Integral SCSI controller 8: Version Fibre Channel QL2342 Port 2
Fabric RAID controller: node 200400a0b811926c port 1 on SCSI controller 8
Fabric RAID lun: node 200400a0b811926c port 1 lun 1 on SCSI controller 8 (primary path)
Fabric RAID lun: node 200400a0b811926c port 1 lun 3 on SCSI controller 8 (alternate path)
Fabric RAID lun: node 200400a0b811926c port 1 lun 5 on SCSI controller 8 (primary path)
Fabric RAID lun: node 200400a0b811926c port 1 lun 7 on SCSI controller 8 (alternate path)
Fabric RAID controller: node 200400a0b811916a port 1 on SCSI controller 8
Fabric RAID lun: node 200400a0b811916a port 1 lun 1 on SCSI controller 8 (primary path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 3 on SCSI controller 8 (alternate path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 5 on SCSI controller 8 (primary path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 7 on SCSI controller 8 (alternate path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 9 on SCSI controller 8 (primary path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 11 on SCSI controller 8 (alternate path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 14 on SCSI controller 8 (primary path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 16 on SCSI controller 8 (alternate path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 18 on SCSI controller 8 (primary path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 20 on SCSI controller 8 (alternate path)
Integral SCSI controller 9: Version Fibre Channel QL2342 Port 1
Fabric Tape: node 500104f0008a1e1b port 2 on SCSI controller 9: StorageTek 9940
Fabric Tape: node 500104f0008a1de2 port 1 on SCSI controller 9: StorageTek 9940
Fabric Tape: node 500104f000901d6d port 1 on SCSI controller 9: StorageTek 9940
Fabric Tape: node 500104f000901d9d port 1 on SCSI controller 9: StorageTek 9940
Fabric Tape: node 500104f000901dcd port 1 on SCSI controller 9: StorageTek 9940
Fabric Tape: node 500104f000901dd9 port 1 on SCSI controller 9: StorageTek 9940
Fabric Tape: node 500104f000901dfd port 1 on SCSI controller 9: StorageTek 9940
Integral SCSI controller 13: Version Fibre Channel QL2342 Port 2
Fabric Tape: node 500104f0008a1e54 port 1 on SCSI controller 13: StorageTek 9940
Fabric Tape: node 500104f0008a1dd9 port 1 on SCSI controller 13: StorageTek 9940
Fabric Tape: node 500104f000901d76 port 1 on SCSI controller 13: StorageTek 9940
Fabric Tape: node 500104f000901da6 port 1 on SCSI controller 13: StorageTek 9940
Fabric Tape: node 500104f000901dd6 port 1 on SCSI controller 13: StorageTek 9940
Fabric Tape: node 500104f000901de2 port 1 on SCSI controller 13: StorageTek 9940
Fabric Tape: node 500104f000901e06 port 1 on SCSI controller 13: StorageTek 9940
Integral SCSI controller 17: Version Fibre Channel QL2342 Port 1
Fabric RAID controller: node 200500a0b80f10bc port 1 on SCSI controller 17
Fabric RAID lun: node 200500a0b80f10bc port 1 lun 1 on SCSI controller 17
Fabric RAID lun: node 200500a0b80f10bc port 1 lun 3 on SCSI controller 17
Integral SCSI controller 23: Version Fibre Channel QL2310
Integral SCSI controller 10: Version Fibre Channel QL2342 Port 2
Fabric RAID controller: node 200400a0b811926c port 1 on SCSI controller 10
Fabric RAID lun: node 200400a0b811926c port 1 lun 1 on SCSI controller 10 (alternate path)
Fabric RAID lun: node 200400a0b811926c port 1 lun 3 on SCSI controller 10 (primary path)
Fabric RAID lun: node 200400a0b811926c port 1 lun 5 on SCSI controller 10 (alternate path)
Fabric RAID lun: node 200400a0b811926c port 1 lun 7 on SCSI controller 10 (primary path)
Fabric RAID controller: node 200400a0b811916a port 1 on SCSI controller 10
Fabric RAID lun: node 200400a0b811916a port 1 lun 1 on SCSI controller 10 (alternate path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 3 on SCSI controller 10 (primary path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 5 on SCSI controller 10 (alternate path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 7 on SCSI controller 10 (primary path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 9 on SCSI controller 10 (alternate path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 11 on SCSI controller 10 (primary path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 14 on SCSI controller 10 (alternate path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 16 on SCSI controller 10 (primary path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 18 on SCSI controller 10 (alternate path)
Fabric RAID lun: node 200400a0b811916a port 1 lun 20 on SCSI controller 10 (primary path)
Integral SCSI controller 25: Version Fibre Channel QL2342 Port 2
Integral SCSI controller 18: Version Fibre Channel QL2342 Port 2
Fabric RAID controller: node 200400a0b80f10bc port 1 on SCSI controller 18
Fabric RAID lun: node 200400a0b80f10bc port 1 lun 0 on SCSI controller 18
Fabric RAID lun: node 200400a0b80f10bc port 1 lun 2 on SCSI controller 18
IOC3/IOC4 serial port: tty3
Gigabit Ethernet: tg16, module 002c10, PCI bus 2 slot 2
Gigabit Ethernet: tg3, module 001c10, PCI bus 2 slot 2
Gigabit Ethernet: tg7, module 001c21, PCI bus 6 slot 2 port 0
Gigabit Ethernet: tg8, module 001c21, PCI bus 6 slot 2 port 1
Gigabit Ethernet: tg17, module 002c10, PCI bus 1 slot 2
Gigabit Ethernet: tg6, module 002c10, PCI bus 5 slot 2
Gigabit Ethernet: tg18, module 002c10, PCI bus 6 slot 2
Integral Fast Ethernet: ef0, version 1, module 001c10, pci 4
Gigabit Ethernet: tg4, module 002c10, PCI bus 4 slot 1
Gigabit Ethernet: tg12, module 001c24, PCI bus 6 slot 2 port 0
Gigabit Ethernet: tg13, module 001c24, PCI bus 6 slot 2 port 1
Gigabit Ethernet: tg9, module 002c10, PCI bus 4 slot 2
Gigabit Ethernet: tg5, module 002c10, PCI bus 3 slot 1
Integral Gigabit Ethernet: tg0, module 002c10, PCI bus 3 slot 2
Gigabit Ethernet: tg19, module 002c21, PCI bus 6 slot 2 port 0
Gigabit Ethernet: tg20, module 002c21, PCI bus 6 slot 2 port 1
Gigabit Ethernet: tg14, module 001c24, PCI bus 4 slot 2 port 0
Gigabit Ethernet: tg15, module 001c24, PCI bus 4 slot 2 port 1
Gigabit Ethernet: tg1, module 002c21, PCI bus 4 slot 2 port 0
Gigabit Ethernet: tg2, module 002c21, PCI bus 4 slot 2 port 1
Gigabit Ethernet: tg10, module 001c21, PCI bus 4 slot 2 port 0
Gigabit Ethernet: tg11, module 001c21, PCI bus 4 slot 2 port 1
IOC3/IOC4 external interrupts: 1
IEEE 1394 High performance serial bus controller 0: Type: OHCI, Version 0x104C-1 0
USB controller: type OHCI |
|
Back to top
|
|
 |
Kassen
Janitor


Joined: Jul 06, 2004 Posts: 7678 Location: The Hague, NL
G2 patch files: 3
|
Posted: Sun Dec 23, 2007 11:23 am Post subject:
|
 |
|
(sorry, missed this post)
My, that's quite the system.
I realise the purpose of such monsters is often sensitive, but I'm quite curious about what this is doing.... _________________ Kassen |
|
Back to top
|
|
 |
elektro80
Site Admin

Joined: Mar 25, 2003 Posts: 21959 Location: Norway
Audio files: 14
|
Posted: Sun Dec 23, 2007 11:44 am Post subject:
|
 |
|
Tetris? _________________ A Charity Pantomime in aid of Paranoid Schizophrenics descended into chaos yesterday when someone shouted, "He's behind you!"
MySpace
SoundCloud
Flickr |
|
Back to top
|
|
 |
BobTheDog

Joined: Feb 28, 2005 Posts: 4044 Location: England
Audio files: 32
G2 patch files: 15
|
Posted: Sun Dec 23, 2007 1:21 pm Post subject:
|
 |
|
The machine is the central server for a Digital Production system for Denmark Radio (www.dr.dk) who are the Danish national broadcaster.
All new Radio and TV productions that DR create are done using this system. along with many other machines for transcoding, editing stations, transmission servers, Ingest stations etc. All these other machines use this central server as glue and storage via xml based calls to multi process piece of software called the BIS, this handles around 500,000 to 2,000,000 transactions a day.
It also has 2PB of offline storage using tape robots to store off-lined hires media, this media can be got at in around 1 minute after a request is made. It has around 70TB of nearline storage, media is automatically offlined if it is not used for a while using DMF. Lowres versions of all media are always stored on nearline storage for instant viewing and edits can be done against this material and then the machine will conform the edits useing the hires material.
The system has a major advantage of working in a "TailMode" way, you can start ingesting video from a camera into the system and edit it as it is ingesting and then transmit the finished clip while the original is still being ingested.
There is also another machine with the same specs for failover, and two more slight lower spec machines for testing and development.
I'm one of the Guys that has developed the system which has taken six years so far with maybe 1 to 2 years left till it is fully finished.
Cheers
Andy |
|
Back to top
|
|
 |
deknow

Joined: Sep 15, 2004 Posts: 1307 Location: Leominster, MA (USA)
G2 patch files: 15
|
Posted: Sun Dec 23, 2007 1:33 pm Post subject:
|
 |
|
would you like to...play a game? |
|
Back to top
|
|
 |
Kassen
Janitor


Joined: Jul 06, 2004 Posts: 7678 Location: The Hague, NL
G2 patch files: 3
|
Posted: Sun Dec 23, 2007 2:23 pm Post subject:
|
 |
|
WOW. _________________ Kassen |
|
Back to top
|
|
 |
blue hell
Site Admin

Joined: Apr 03, 2004 Posts: 24383 Location: The Netherlands, Enschede
Audio files: 296
G2 patch files: 320
|
Posted: Sun Dec 23, 2007 3:16 pm Post subject:
|
 |
|
Andy I think I understand now why you need a little extra nicotine intake occasionally, this is wild  _________________ Jan
also .. could someone please turn down the thermostat a bit.
 |
|
Back to top
|
|
 |
|