Welcome, Guest
Username: Password: Remember me

TOPIC: BruceX: Try this new Final Cut Pro X benchmark

BruceX: Try this new Final Cut Pro X benchmark 10 Mar 2018 17:14 #94560

Mac Pro 3.1 (8 core)
Processor 2 x 3,2 GHz Quad-Core Intel Xeon
Memory 24 GB 667 MHz DDR2 FB-DIMM
GPU NVIDIA GeForce GTX 780 3072 MB
500GB WD Black

BruceX: 44 sec.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 21 Mar 2018 14:50 #94756

  • rwillett
  • rwillett's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 20
  • Thank you received: 5
  • Karma: 0
You won't get a lot (any?) benefit from RAIDing as the benchmark is designed to stress graphics cards. Very little writing is done,. I recall we did that and it made no difference with real hard disks as opposed to SSDs,
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 08 May 2018 01:11 #95427

  • zzchu
  • zzchu's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 69
  • Thank you received: 8
  • Karma: 3
MacPro 5,1 (Mid 2010) 3.46 Ghz 6-core
Sapphire Radeon RX 580 Pulse 8gigabyte
FCPX 10.4.2 and Mac OS 10.13.4.
Export to ProRes:
21.92 seconds
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 08 May 2018 01:43 #95429

  • FCPX.guru
  • FCPX.guru's Avatar
  • OFFLINE
  • Platinum Boarder
  • bbalser.com
  • Posts: 2533
  • Thank you received: 329
  • Karma: 32
iMac Pro, 10 core, 3.0GHz, 64 GB RAM, Vega 64
Exporting to Promise Pegasus 32 TB (28TB usable), 8 bay, Thunderbolt 3, RAID 5
No pre-rendering

Using the version of the test currently linked in the OP. Is there an update to this?

H.264
24.33 seconds avg

ProRes 422
20.8 seconds avg

Just for fun, H.264 exported to the internal 2TB SSD drive, 25 seconds. So, never edit on your system drive, it's not necessarily the fastest.

What I find interesting is that I do 30 second TV commercials in 4K, export to ProRes, in much less time. Which is real-world work, so I base my opinions on that. But this is a fun test. I wonder if folks hit the start on their stop watches when they hit the save button or when the background task clock starts moving.
Last Edit: 08 May 2018 02:22 by FCPX.guru.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 08 May 2018 10:28 #95434

  • martinX
  • martinX's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 65
  • Thank you received: 6
  • Karma: 0
24.4 for h.264
18.6 for ProRes

Model Name: iMac
Model Identifier: iMac18,3
Processor Name: Intel Core i7
Processor Speed: 4.2 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 24 GB
Radeon Pro 580 8192 MB
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 21 Jul 2018 21:41 #96435

  • ti.jl
  • ti.jl's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 2
  • Karma: 0
33.9s for ProRes 422

Model Name: Hackintosh
Model Identifier: iMac12,1
Processor Name: Intel Core i7
Processor Speed: 3.41 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Nvidia GTX1070 8GB
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 21 Jul 2018 21:50 #96436

  • ti.jl
  • ti.jl's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 2
  • Karma: 0
Not bad for a hack from the green team...
32.90 for ProRes

Model Name: Hackintosh - Asus P8P67 Evo
Processor Name: Intel Core i7 2600K
Processor Speed: 4.2 GHz
Number of Processors: 1
Total Number of Cores: 4, 8 threads
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB 1333 Mhz DDR3
SSD: Crucial 240GB SATA 2
Nvidia GTX 1070 8GB
Attachments:
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 22 Jul 2018 09:00 #96440

  • joema
  • joema's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 1125
  • Thank you received: 236
  • Karma: 20
My latest tests on 2017 top-spec iMac 27 and 10-core Vega 64 iMac Pro, all running macOS 10.13.6 and FCPX 10.4.3. Each test was done five times on five fresh libraries to avoid caching effects, and the average taken.

Background rendering was off, timeline was not pre-rendered, Time Machine was shut down. Ideally when doing benchmark testing Spotlight should be shut down but I didn't do that.

To improve timing precision, I would suggest everyone subsequently copy and paste the BruceX timeline to itself 4 times and divide the resulting execution time by 4. However -- these numbers aren't directly applicable to the previous single-pass numbers, but somewhat faster. This might imply a significant % of BruceX timing is startup overhead and isn't really measuring the core task. Conversely it might imply the 4x timeline is benefiting from cache effects of the repeating test. This shows how complex a simple-looking benchmark can be. Until this is understood or Alex posts an "official" new test procedure, I recommend we keep running it as usual.

However there is considerable run-to-run variation, so it's a good idea to run several iterations and take the average. Definitely background rendering should be disabled.

Time was started when hitting the share button and stopped when the file loaded in Quicktime Player. I tested both ProRes 422 and H264 4k using "fast" export option. Note the H264 export is 4k not 5k.

2017 iMac 27, ProRes 422: 17.9 sec
2017 iMac 27, H264 4k: 19.0 sec

2017 10-core Vega 64 iMac Pro, ProRes 422: 12.2 sec
2017 10-core Vega 64 iMac Pro, H264 4k: 15.3 sec
Last Edit: 22 Jul 2018 09:03 by joema.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 25 Jul 2018 00:32 #96473

  • qbe
  • qbe's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 19
  • Thank you received: 2
  • Karma: 1
joema: very very interesting findings
Last Edit: 25 Jul 2018 00:32 by qbe.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 10 Jan 2019 23:26 #98458

  • solidww
  • solidww's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 16
  • Thank you received: 2
  • Karma: 1
Quick question for everyone. I am planning to build a new Hackintosh. For best editing in a 4K workflow with FCP X. Would sticking with the two current 7850 be good or would any of you upgrade to two RX560s? I could also go with a single 7950 GPU, if that would be the better bet?

I mostly shoot with my iPhone at 4k. So, I don't necessarily need the faster most powerful GPUs.

Thank you for any help.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 20 Feb 2019 16:07 #98986

  • John Vito
  • John Vito's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 4
  • Karma: 0
John Vito wrote:
I've finally upgraded my 4+ year-old Hackintosh to Sierra from Mavericks.

Hackintosh
Intel Core i7 3.39 GHz Sandy Bridge
256 SSD
32 GB 1600 MHz DDR3
EVGA GeForce GTX 560 2048 MB
OS - Sierra 10.12.3
FCX 10.3.2

Yikes! Rending time ave: 168 seconds

My guess the reason for the slow time is the video card. I'm running dual monitors from the card, I'm sure that doesn't help.

UPDATE
I just replaced the above EVGA GeForce GTX 560 2048 MB card with a Sapphire R9 280X 3GB graphics card. Ran BruceX and as always followed the instructions. The R9 280X is over 4 times faster than the GeForce!

Hackintosh
Intel Core i7 3.39 GHz Sandy Bridge
500 GB SSD
32 GB 1600 MHz DDR3
Sapphire R9 280X 3GB
OS - Sierra 10.12.6
FCX 10.4

Rending time ave: 37 seconds!
Last Edit: 20 Feb 2019 16:10 by John Vito.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 05 Mar 2019 12:50 #99158

  • verstaerker
  • verstaerker's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 61
  • Karma: 0
17s for ProRes 422
44s without the eGPU

Model Name: MBP 2016
Processor Name: Intel Core i7
Processor Speed: 2.9GHz
Number of Processors: 1
Memory: 16 GB
BM eGPU Pro Vega56
Last Edit: 07 Mar 2019 17:32 by verstaerker.
The administrator has disabled public write access.