Please help with a new dual purpose PC build

Question

Hi everybody in AdobeLand! 
I've been reading various boards and hardware sites and have started piecing together a dual purpose computer system.  It will be used for both video editing (of pre-shot hacked, high bitrate I-Frame Panasonic GH2 DSLR and camcorder footage using the AVCHD codec @ 1080p 24 and 30 fps) and webcasting/streaming purposes.  I would build two computers for each task, but it's just not in the budget right now.  I'm already stretching things as is. 
I'm still not sure if I will be using Adobe Premiere or Sony Vegas Pro 12 yet, though it seems like they organize their folders and file structures about the same.  Adobe's cloud service has me a bit scared off right now.  This new scheme feels like they have their hand purpetually in your wallet, which does not sit well with me.  I may still go with Vegas 12 just to avoid that hassle right now.  Help guide me here, experts!  Telestream's Wirecast is being used for multi-cam switching and graphics for live and pre-recorded material being compressed and streamed. 
Back on topic:
Here's the build as of right now...
OS: Windows 7 64-Bit Professional (Windows 8 absolutely sucks!)
CPU: Intel i7-4930k 6-Core Ivy Bridge (own)
Motherboard: Asus P9X79 Pro (own)
Memory: Crucial Ballistix 1.35v Sport DDR3L @ 32 GB (own)
GPU:  EVGA GTX 770 FTW w/ 4 GB (will buy another HD monitor at a later date, hence the 4GB memory)
Case:  Fractal Design XL R2 Full Tower
CPU Cooling:  Noctua NH-D14 w/ SE2011 Bracket
PSU: Corsair RM1000 Quiet Series / 80 Plus Gold / 1000 Watts
Monitor: Dell U2412M Ultrasharp 24 inch / 1920x1200
Optical Drive: LG Blu-ray Writer
Keyboard: Microsoft 4000 Ergonomic
HDMI capture cards: Blackmagic Designs Decklink Mini (x2)
Storage:
I bought two Samsung 840 Pro SSD drives:  one 128 GB and one 256 GB
Thinking about possibly 2 (maybe 3-4 if I really stretch) Seagate ST3000DM001 3TB HDD's.
I could sure use your help with any advise on arranging the storage to get the best bang vs. buck in speed and storage utilization (Wirecast can be setup to record live webcast sessions at 720p or 1080p in compressed files... probably no more than 120 minute webcasts... so that comes into play as well).  Just don't have the funds for an uber-expensive RAID controller card right now.
Any opinions overall on the parts for the current build?  I still have time to send back and exchange anything already purchased.
Thank you for your time and consideration.   

Answer 1

What do you not understand from:
With all the reading and writing going on, on the boot disk, it is understandable you need a (number of) dedicated disk(s) for video editing, especially with the bandwidths required when the clip duration is short and the number of tracks exceeds one and uses a codec more complex than DV. The kind of files used during editing are, in order of their need for speed:
Media cache & Media cache database files, created on importing media into a project. They contain indexed, conformed audio and peak files for waveform display.
Typically small files, but lots of them, so in the end they still occupy lots of disk space.
Preview (rendered) files, created when the time-line is rendered for preview purposes, the red bar turned to green. Read all the time when previewing the time-line.
Project files, including project auto-save files, that are constantly being read and saved as auto-save files and written when saving your edits.
Media files, the original video material ingested from tape or card based cameras. Typically long files, only used for reading, since PR is a non-destructive editor.
Export files, created when the time-line is exported to its final delivery format. These files are typically only written once and often vary in size from several hundred KB to tens of GB.
When you are doubting which category of files to put on which kind of disk, especially when using both SSD's and HDD's, keep in mind that the speed advantage of SSD's over HDD's is most noteworthy with the Media cache & Media cache database. These files are frequently accessed, are small and there are many, so reducing latency and seek times and increasing transfer rates pays off by putting these on a SSD, rather than on a HDD, even if it is a raid0. Export files can go to the slowest volume on your system, since you only export once. To help you decide, I have added priority rank-numbers for speed, with 1 for the fastest volume and 5 for the least speed-demanding category.
and
Well, in the benchmark tests we have not seen any noticeable difference between SSD and HDD in terms of performance, but logic dictates that there should be a small difference in performance when the volume used for media cache is a SSD, because of the much faster access time and lower latency compared to a conventional disk. If it is noticeable, it is specifically on this volume with the media cache and media cache database, due to the large amount of small files that need to be accessed and written. This argument does not apply to the media volume with a limited number of files, that are very big in size.