I said here
http://ddisoftware.com/tech/qimage-ultimate/v2013-120-issuescomments/msg13675/#msg13675
that “it (v120) makes my user experience so much better”
Let me try to justify that statement.
When I changed my camera last year and went from one that produced 8MB raw file to one that made 24MB files, the time difference to make the raw cache and wait before I could get going with refining and editing a batch of images was noticeably longer. The introduction of v120 with “super fast raw processing” has now made the work flow much faster than v119 was with 8MB raw images.  
Like Fred, I did some timing’s late last night; my quad core PC has a slightly later, more powerful processor that Fred’s so equivalent raw images are quicker to process here.

Time to make an image available for refine or image editing:
First Canon 600D CR2 images ~ 24MB (timed with 10 images)
V119: 52 secs
V120: 2.0 secs (edit corrected)
 Second, I have a number of Nikon D800 raw images ~ 74MB, although some samples are 45MB: (timed with 1 image)
V119: 36 secs
V120: 10 seconds

One aspect of version 120 that is particularly helpful to me is in using the image editor. Most of you will know it’s possible to click a button and go to the refine screen from the editor and back again. Previously that required the “final” raw cache for that image to be re-built but now the new concept of using a temporary “draft” cache image is exploited to make the refresh of the editor screen very much quicker & smoother.
How do I know about the new “draft” cache? In the editor, helpful colour coded messages appear, see attached screen shots.
The first shot shows the initial editor message after clicking “save” in the refine screen. That very soon disappears and the image is ready again for editing. However, you are still kept informed as what QU is doing: the second and third shots show new messages about the status of the raw cache.
Now, can I spot the difference on-screen when it changes from draft to final raw cache    
It seems that while I’m busy refining or editing, the final cache is being made in the background without affecting in any way me getting on with the job – nice!  
So what happens when I print, I’ll have to check?
Terry

I don't think Fred can add up  
Regarding time differences with a new folder of images, I went down to my local village green so get a fresh batch of images and resisted the temptations the local pub to take 27 photos, see attached.
It took just 52 seconds for all the images to acquire the green dot and every one was ready for refine and edit. Version 119 would have taken 2mins 15 secs.
Extrapolating to a batch of say, 100 images, that would be about 3mins 12 secs for V120 and 10mins 48 secs for V119. That is a saving of  over 7 minutes    

I had always accepted the previous timings for cache building as a small price to pay for better performance in later processing, but now it's a whole new ball game.
Well done Mike  
Terry