• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

[HELP] CPU / GPU Rendering Calculations

Joined
Sep 25, 2007
Messages
278 (0.05/day)
Hello everyone,

Before I render such a large project @ 4K resolutions (3840 x 2160) for a friend, I would like some help with maths to calculate the time, so, I can see the 'estimate' finish time. But, from what I see on other websites, they calculate render time like this without output resolutions:

CPU Core / per machine x Frequency (GHz) x HRS x Render Price = Price (TOTAL Price x Frames)

For rendering, I got 2 machines and I want to help him render. I would like to work out estimate... so how do I work out "output resolutions, time, price" and mathematical GPU rendering method?

Help, please?

Machine 01 - WS Primary BOSS - Backbunrer Manager
CPU: Intel Xeon E5-1650 V3 @ 3.5GHz (6 Cores, 12 thread)
Memory: 64GB DDR4 @ 2133MHz
GPU: Nvidia GTX TITAN X 12GB

Machine 02 - WS Support (SLAVE)
CPU: Intel Xeon E5-1650 V3 @ 3.5GHz (6 Cores, 12 thread)
Memory: 64GB DDR4 @ 2133MHz
GPU: Firepro W7000 (4GB)

Example I tried. But, I don't know how to work everything out exactly... I don't know where or how to add resolution + time calculations. :(

6 Cores /MCH x 3.5GHz x 0.333 HRS x 1 Frames x 0.50 USD = $3.40 USD

2 Machine @ 3.5GHz x 2 = $6.80 USD
 
Last edited:
Joined
Feb 8, 2012
Messages
3,013 (0.68/day)
Location
Zagreb, Croatia
System Name Windows 10 64-bit Core i7 6700
Processor Intel Core i7 6700
Motherboard Asus Z170M-PLUS
Cooling Corsair AIO
Memory 2 x 8 GB Kingston DDR4 2666
Video Card(s) Gigabyte NVIDIA GeForce GTX 1060 6GB
Storage Western Digital Caviar Blue 1 TB, Seagate Baracuda 1 TB
Display(s) Dell P2414H
Case Corsair Carbide Air 540
Audio Device(s) Realtek HD Audio
Power Supply Corsair TX v2 650W
Mouse Steelseries Sensei
Keyboard CM Storm Quickfire Pro, Cherry MX Reds
Software MS Windows 10 Pro 64-bit
GHz is around billion cycles per second, and you use time in hours without converting to seconds ... that's bad mkay.
That's first thing that comes in mind ... I'm too lazy to see if your formula makes sense :oops:
 
Joined
Jul 25, 2006
Messages
12,147 (1.87/day)
Location
Nebraska, USA
System Name Brightworks Systems BWS-6 E-IV
Processor Intel Core i5-6600 @ 3.9GHz
Motherboard Gigabyte GA-Z170-HD3 Rev 1.0
Cooling Quality case, 2 x Fractal Design 140mm fans, stock CPU HSF
Memory 32GB (4 x 8GB) DDR4 3000 Corsair Vengeance
Video Card(s) EVGA GEForce GTX 1050Ti 4Gb GDDR5
Storage Samsung 850 Pro 256GB SSD, Samsung 860 Evo 500GB SSD
Display(s) Samsung S24E650BW LED x 2
Case Fractal Design Define R4
Power Supply EVGA Supernova 550W G2 Gold
Mouse Logitech M190
Keyboard Microsoft Wireless Comfort 5050
Software W10 Pro 64-bit
Joined
Sep 25, 2007
Messages
278 (0.05/day)
GHz is around billion cycles per second, and you use time in hours without converting to seconds ... that's bad mkay.
That's first thing that comes in mind ... I'm too lazy to see if your formula makes sense :oops:

Thanks!
 
Joined
Jul 25, 2006
Messages
12,147 (1.87/day)
Location
Nebraska, USA
System Name Brightworks Systems BWS-6 E-IV
Processor Intel Core i5-6600 @ 3.9GHz
Motherboard Gigabyte GA-Z170-HD3 Rev 1.0
Cooling Quality case, 2 x Fractal Design 140mm fans, stock CPU HSF
Memory 32GB (4 x 8GB) DDR4 3000 Corsair Vengeance
Video Card(s) EVGA GEForce GTX 1050Ti 4Gb GDDR5
Storage Samsung 850 Pro 256GB SSD, Samsung 860 Evo 500GB SSD
Display(s) Samsung S24E650BW LED x 2
Case Fractal Design Define R4
Power Supply EVGA Supernova 550W G2 Gold
Mouse Logitech M190
Keyboard Microsoft Wireless Comfort 5050
Software W10 Pro 64-bit
GHz is around billion cycles per second
For the record, 1 GHz is exactly 1 billion cycles per second or 1,000 MHz.
 
Top