At 1): The swap file is evenly distributed over the two WD Raptors, 6 GB of swap file each.

At 2): RAID-0 will almost double the transfer speed, but it will NOT improve access time. Since Windows (and all other modern operating systems) consist of many processes, many of which can access drives, it's smarter to have Process A access disk 1, while at the same time Process B accesses disk 2. If disk 1 and 2 were combined in a RAID 0 array, both processes would compete for the same disk.
Since most of the tasks my computers do involve many small disk transactions, it's smarter to make those transactions independent by having them access independent disks. Only when you do very large file transfers (think harddisk recording), the increased transfer rate of RAID 0 offsets the cost of shared access. And even in the case of harddisk recording I'd recommend placing the OS on its own separate drive, so that its drive access does not interfere with the recording.

At 3): FFRender is the separate process that Poser 7 can start. Poser process means an in-process render. So I meant it exactly the other way around.

At 4) The funny part was that the actual rendering didn't take that much time. Loading objects was the most time consuming phase in the renders, and loading objects has to do with drive access. Anyway, my task manager told me that while Poser was loading objects it used only 1 core.

Now if I would render again at 1600x1600 resolution, I'd expect the actual render time to quadruple, and I'd expect the object loading time would be less influential.

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff