In the search for a APG-hardware as fast as possible I have bought me a OCZ Revodrive3 to check it out. Thought I would share some info in the forum, so here are the first impressions: It's fast, but not as fast as my SSD raid (8xSDD on a LSI 9280 controller) It's a affordable (the LSI raid is not !) For the spesifics see the image below.
My plan, for now, is: 1) OS - samsung 830 SSD 2) OS pagefile - LSI raid 3) OS temp - LSI raid 4) APG temp/scratch - LSI raid 5) APG sourcefiles - RevoDrive3 6) APG destinationfile - SSD4
5 is exactly what I am gonna do also. Can be combined with 6 als reading sourcefiles is mostly not at same time as writing the results. Like the 480 version a lot because of it size and would prefer it before the faste 240 GB version. Speed is good but only if you can have the total project on the disk.
2,3 and 4 I have already on a SSD, but might enjoy each their own small SSD
1 i understand but i would easily be happy with a normal HD there.
I am thinking about a new machine to do my panoediting and previewing. rendering can be done on my i7 920 16 GB machine, but i need a faster machine to work at. Wondering if it will be cost/effective and still superfast to buy six revodrives9some 120- some 240 gb) and put them onto a nice motherboard with 32 to 64 GB of memory. add a 4 gb 256 BIT GPU and presto.....?
several boards have 6-7 PCIe slots, but you could run into trouble with the Option ROM on the mainboard, unless the first card will cater for all the cards, I tried with two cards of the original revo, but i could not get it to work on my board.
you can have a look at the PTGui speedtest with last effort, adding 20x SSD's :-)
I was not thinking about RAID, just use every revodrive as a single drive, according to the function 1 to 6 you mentioned.
I have revised the plan and are for the time beeing running this setup: 1) OS - samsung 830 SSD C: 2) OS pagefile - LSI SSD raid0 E: 3) OS temp - LSI SSD raid0 E: 4) APG temp/scratch - LSI SSD raid0 E: 5) APG sourcefiles and destination - RevoDrive3 F:
Writing the resulting file (often 3+GB) to the sourcefile drive won't be slowed down by reading activities, since the temp-files is on another drive: Reading temp-files from E: writing resulting file to F:
Maybe a Revo can replace the LSI raid, that is two Revos side by side. It would be much cheeper, but not as fast. I'm a bit worried for issues, though.
what sort of transfer do you get in real life, as if you move or copy files in windows, what does the little window report to you? In the same test as you I get 3-4GB/s probably also due to my 4GB cache, but I really only get 1GB/s when I look at transfers and that is also if I then try to calculate the time it took with the given data size.
Maybe there is one more thing to consider: for the APG temp/scratch I guess that iops is more relevant than read/write speed. This disk is peppered with hundreds of small files. for the APG sourcefiles and destination sequential read/write speed is probably of more importance than iops
If this is the case I will have to swap the LSI and the Revodrive, since it seems like the Revodrive has better iops performance for 4K files threaded. When there is some spare time I will look more into this.
the way i see this is that the Revo should be your scratch disk, because of the better 4k and keep the RAID for large files like project and source files as it performs better in the large file size eg. 16mb results
did you do any system tests of your setup, prior to changing your harddrive configuration. In theory spreading out the hard drives sounds good, but by concentrating the hard drives to a fast RAID-0 may be sufficiently faster, but still keep at least three disk setup as in OS/APPs - Temp - Source and Destination. I suppose you could breakup Source and distination files into two Arrays, but then i would keep them on two different RAID controllers.
How many channels are on your 9280? Do you have PCIe 3 on your motherboard? reason I am asking is that I find that I can max out PCIe 2 with 6-8 disks or at least it seems to plateau out on my machine.
try to run the PTGui Speed test on your system before and after making changes, you can use AGP as the test software instead of PTGui - the only reason i mention this test is that it relates to what we do here, and i don't know of any other benchmark tests that test pano's
I hope this makes sense - sorry I am at home sick atm so I might be a little fragmented ;-)
The LSI has 16i and 4e channels. The raid0 consists of 8pcs Intel X25-E 32GB SSD. These are "old", but they are SLC and therefore relative fast. The card is 8x and and take 6Gb/s per port. 8x gen2 means theoretically maxout at 4GB/s. I'm not there (yet). (The Revodrive a x4 card.)
I will run the PTgui speedtest using APG later and tell you what I see.
I have run the PTgui speedtest. But it is not relevant for the discussion on iops vs sequential speed because the image set is too small ! The pano consisting of 337 JPG images ran entirely in RAM, there was no disk activity at all. And there were a lot more of free RAM see image below. For the iops vs sequential I have to pick a much larger pano. I will try that some day later.
So I clocked the result to be 5min 5 sec in both cases.
The rendered image was ugly with lot of issues in the sky. I don't know why and I did not try to find out. I just ran the .autpano projectfile as it was.
As I have to process more and more panoramas it also needs to be done faster and faster. Having the sourcefiles on a SATA-SSD is not fast enough anymore during loading and editing, too much waiting. Do I invest 500 euro into ultimate speed (OCZ-RevoDrive-3-X2 RAId-0, 1500 MB/s 200000 IOPS) or do I go for good speed and more size so I can keep more project on SSD (OCZ-RevoDrive-3 480 GB,1000 MB/s 130000 IOPS).
Or should I use my current revodrive 3 (111 GB 975 MB/s 120000 IOPS ) for the sourcefiles and use the OCZ-RevoDrive-3-X2 RAId-0 for scratch?? having 240 GB scratch file might also help while rendering as now sometimes I see autopano filling up the 111 GB on temp-files and going to secondary tempdrives. Not a big problem but it is a slowdown..
BTW a big project in my case has 30 GB of sourcefiles and consists of 30 panoramas.
My feeling per now is that you need a really fast sequential read/write disk for the source files and the resulting file. Not so important with high iops here. The scratch-disk need to have as high iops as possible, because APG is peppering this drive with lots of small files, read and write. I have not tested this yet, so it is a hypothesis
Then there is the "hard fault s/sec" issue. When APG has eaten all the available RAM windows starts swapping. That is writing RAM to the pagefile and back. This slows down things a lot ! To fight this you have to put the windows pagefile on a drive with as high iops as possible.
Rendering I often do when away from my workstation for long time, so not that important to me. I don't mind a bit of swapping as long as it does not wear down my machine too much or slows things down. It is the speed when I am editing etc. that counts for me
So if I would have only have about 4-500 euro and therefore can only buy one Revodreive-3-x2 240 GB, that would mean the old revo for sourcefiles ( 975 MB/s is less then 1500 MB/s but much better then sata) and new RevoDrive-3-x2 240 GB for scratch files AND the pagefile. later i can always buy another revodrive for the pagefile, when money cames in.
This afternoon things looked like this at my machine, things maxed out ;-)
I guess that your system is near optimum if you manage to keep the CPU at max through most of the render stages. Lots and lots of RAM will do all of the tricks in RAM. It is not possible to mimic this with SDD's or SDD's in raids for the pagefile.
My current mobo is limited to 16 GB, so in time it will need to be replaced by one that can hold like 96 MB. My upgradepath is to buy and use already some parts that can be used very well in that new machine later but also help the current machine. The revodrives are certainly parts like such. After adding one or more Revodrives I will start looking for a new mobo and CPU and start it up with initially something like 32 GB and the revodrives I already have. Then step by step add extra memory once I can afford it.