How can we tell...
We cant see what results or performance you are getting.
We cant see how your system is set up.
We dont know whatgraphic card you have installed or intend to buy.
We do know an I5 is generally of lesser performance than an I7 though.
Just remember that your results from PPBM5.com should be compared to other users with comparable hardware, as well as the same version of Premiere Pro (CS6 can be slower than previous versions).
It isn't the score that matters. What you want to know is, are you getting the same results as other people. That should tell you if you have it configured correctly. If yours is slower, there are many possible reasons.
Thanks so much for the replies. Yes, benchmark tests would be more beneficial. Ran the PPBM test and got:
But can't figure out what they mean ... are they the times for each render?
Also attached a Geekbench score with numbers that seem awfully low:
Wondering if I have screwed up somewhere...
You should submit your results and you will see your score to compare with others. However, if I am reading those numbers correctly, they are horrible for a PC bought in the last year. Your disk speed is a huge bottleneck. To heck with SSD. You need decent 7200 rpm drives. And more than one drive.
Editing 4K on that PC would initiate suicidal thoughts in me, I don't know about you.
I have received your submission, but am unclear what the correct figures are.
In your post you said 125, 144, 114 and 60. In your submission the figures are 121, 149, 362 and 60. Especially the 114 versus 362 is worrisome. What happened on your system to give these widely different results?
Your Geekbench score of 11380 is pretty much in line with other i7-3770 CPU's, which show 11436 as the average score. For comparison, I did the same Geekbench test and came up with:
Or with the 64-bit version:
With CS6 and your video card, there is one thing that stands out and that is your H.264 test, which is heavily dependent on CPU efficiency. Whether the score is 114 or 362 makes a huge difference. With 114, it is a meager result, with 362 it is disastrously bad. It can indicate that there are a number of background processes and services running that steal CPU cycles during the test.
What have you done to tune your system? Turned off indexing and compression on both disks, turned off Aero, removed the Sidebar, MSN, disabled all Apple processes like mDNSResponder, iTunes, etc. Killed jusched.exe and similar stuff? Disabled services not needed in line with BlackViper suggestions?
Please let me know what changed your scores so dramatically and which figures are the accurate ones to enter into the database.
[moved to hardware forum]
Did you completely uninstall all of the drivers from your old AMD installation before you switched motherboards? (Or better still, completely wipe out your Windows drive and reinstall Windows from scratch?) You see, the incompatible motherboard drivers might have caused conflicts with your new Intel-based system.
In addition, I assume that you are using a non-CUDA GPU (which cannot utilize MPE GPU acceleration at all whatsoever, and thus permanently locks Premiere Pro to the software-only mode).
With that Radeon HD 4670 and old-generation disks not in RAID, no wonder why you got relatively poor performance scores all around, even at 114 seconds in the H.264 Blu-ray encoding test. But with that 362-second H.264 score that's officially on the PPBM5 list, there is a huge bottleneck somewhere in that configuration.
Thanks for the advice folks. I found that I had improperly installed my RAM sticks for dual-channel access. I apologize for being an imbicile -- and not reading my manual thoroughly.
After turning off many background processes and rearranging my RAM, here's the scores I came up with: 119,133,108,60.
Considering old video card and older non-raid disks not in RAID, are these numbers ok?
Hopefully here in a couple months I'll be able to afford SSD and some insane video card, I just want to be sure this CPU/Mobo/ram combo forms a good basis for a new video editor (dslr/non-4k).
I'll modify your data tomorrow.
That's about what is expected given the non-MPE-capable GPU and the slow-ish disks. A total of 420 seconds, with an RPI close to 8 if not over.