Zoho Sheet - renderfarm capacity and needs analysis worksheet

Calculator


Renderfarm Capacity Analysis worksheet

The Section Below will help Calculate the Studio's Existing Rendering Capacity
Instructions	Enter data into the fields below	NOTES	Calculated Results (Existing Capacity)
TOOL CALIBRATION CONSTANT number of hours in a month (720 is default)	720	This field should be kept at "720" (30 days x 24 hours/day) except for special cases	SECONDS of RENDERED animation REQUIRED per month (@ 30 frames per second)	83
# 1. enter the monthly rendering workload (in # of rendered frames )	2500	This data should be known by the studio manger or art director	SECONDS of RENDERED animation REQUIRED per month (@ 24 frames per second)	104
# 2 enter measured average Cinebench 10 Multi CPU score (CB-CPU points) for customer's current rendernode(s) ***If 32bit version of Cinebench10 is used, then add about 8% to their score and enter it here	11,500	This benchmark data will come from customer's benchmark results running the Cinebench10 test on all exisiting rendernodes This number is the average CB-CPU score of all available rendernodes	Total rendering capacity (in CB-CPU points) (64bit Windows) for existing farm:	6900
# 3 enter current # of computers currently being used for rendering	1	This data should be known by the studio manger or art director. This number can include "part-time" rendernodes	Total rendering time (in hours) required for indicated workload using existing hardware	2500
# 4 enter total (average) number of frames that can currently be rendered on all existing computers in one hour (typical or maximum scene complexity)	1	This data should be known by the studio manger or art director	% monthly utilization of current rendernodes for indicated workload *Numbers over 100% indicate exceeded inhouse capacity for indicated workload	578.7%
# 5 enter the Maximum Percentage (%) of time the current rendernodes are available for rendering tasks	60.00%	this number can include any "part-time" rendering nodes. A value of "100" would indicate all rendernodes are available 24 hours/day	Aggragate CB-CPU point/Hrs required for indicated workload	39931


The Section below will help calculate how many new BOXX units are required for given workload
	Enter data into the fields below	NOTES
TOOL CALIBRATION CONSTANT number of nodes per chassis ("2" is default for 10300)	2	This should stay at "2" for normal use with renderBOXX 10300 units. Use "1" if 3DBOXX workstation is to be used for rendering instead of renderBOXX 10300	Calculated Results -(Proposed New Capacity using renderBOXX 10300)
# 7 enter number of new renderBOXX 10300 modules being considered	1		total number of new rendernodes (remember its 2 per 10300 module)	2
# 8 enter measured Cinebench CB-CPU rendering performance of each renderBOXX 10300 node (see below for proper value to type here)	23,000		total (aggregate) rendering capacity (in CB-CPU points) for the indicated new 10300 modules	46000
Use the following values: Dual Xeon 5520 - 23,000 Dual Xeon 5540 - 24,800 Dual Xeon 5550 - 26,400 Dual Xeon 5570 - 28,000 Dual Xeon 5580 - 31,000 Dual Xeon 5590 - 32,900			total rendering time (in hours) required for indicated workload using indicated number of 10300 modules	375
			% monthly utilitzation of proposed new rendernodes for indicated workload *Numbers over 100% indicate exceeded inhouse capacity for indicated rendering workload	86.8%





Capitol Cost Calculations
	Enter data into the fields below		Calculated new hardware/software Cost Results
# 9 enter the cost of each new 10300 module	$6,000.0		total hardware + software cost for new 10300 modules	6000
# 10 enter the cost of additional software for each new 10300 NODE (per node - not per module)	$-		mothly cost on 3 year commercial lease	199.2
Temporarily DISABLED enter the cost of additional items needed for new renderfarm (that can be added to the lease)	$-		rendering cost per frame of animation	1.91

Calculate the Cost for sending indicated rendering workload out-of-house			Calculated Cost for sending rendering "out of house"
Enter the Ghz/Hr rate charged TO studio BY commercial rendefarm (RenderTitan) service for rendering (typically 12.5 cents per Ghz/Hr.)	$0.200		GHz/Hours required for indicated rendering workload	7500
http://www.rebusfarm.com/price-list_en.html	starts at about 9.9 cents per GHz/Hr		Cost charged BY commercial rendefarm (RenderTitan) service for rendering indicated number of frames	4761
http://www.rendertitan.com/estimate	starts at about 12.5 cents per GHz/Hr		Out-of-House rendering cost per frame of animation	1.9
http://www.renderrocket.com/estimator.aspx	starts at about 20 cents per GHz/Hr

customer report



Customer Report


Studio's current rendering capacity (based on customer's stated workload)
Total currect in-house rendering capacity	432	frames
Total monthly rendering volume required to meet business demand	2500	frames
% Utilization of current in-house rendering capacity	578.7%	numbers over 100% indicate exceed in-house capacity


Enhanced rendering capacity using proposed BOXX hardware (based on customer's stated workload)
Total proposed rendering capacity	16667
% Utilization of proposed new rendering given statem current rendering workload	86.8%

formulas

BOXX Renderfarm Capacity/Economics Worksheet
Based on normalization of factors using standized Cinebench scores


BLUE indicates required input (these are inputs for the calculated results)
ORANGE indicates calculated results


Current Customer rendering Capacity
enter the # of required monthly rendered frames	2500
SECONDS of RENDERED animation per month @ 24fps		104.2	SECONDS of RENDERED animation per month @ 24fps	83.3
enter measured avarage Cinebench CB-CPU points (64bit windows) for current rendernodes	6900
enter current # of nodes on current farm	1
enter avarage number of frames (typical or maximum complexity) that can be rendered on extiting renderfarm in one hour	1
enter current average CPU clock speed (In Ghz)	2.4		used for "sanity check" against CB-CPU score and/or for alternate performance calulations
enter average number of cores per node	4		used for "sanity check" against CB-CPU score and/or for alternate performance calulations
total number of cores in current renderfarm		4	used for "sanity check" against CB-CPU score and/or for alternate performance calulations

		6900	:total # CB-CPU points in existing farm
		5.79	max. total frames per hour per node
		5.79	max total frames per hour (total)
		2500	max total frames per month (possible)
		720	number hours in month
		432	weighted number hours in month
		432	max total frames (weighted by % node availablility)
		432.00	total max FRAME rendering capacity (weighted by % node availablility)
		2500	:total renderfarm time (in hours) required for indicated workload
		2.76	CB-CPU points per frame
		5.79	:% renderfarm utilitzation **Numbers over 1.00 indicate exceeded inhouse capacity
		39930.6	Aggragate CB-CPU point/Hrs required for indicated workload
		9.52	# GHz/hr available on current farm
		4113.5	# Ghz/hours available on current farm
		23805	total Ghz/hrs required for workload
		60.00%	total % of times rendernodes are available for rendering tasks
Proposed renderBOXX renderfarm solution
enter number of new renderBOXX modules are planned for purchse. (2 nodes per module)	1	2	:number total new rendernodes
enter CPU model # or speed new renderBOXX modules are planned for purchse?	1
measured rendering performance of each node in CB-CPU points (64 bit windows) based on selected CPU speed ***(This field should ulitmately be automated using our internal benchmark data -and the value here should be automatically populated based on CPU type selected above)	23000	46000
		46000	:aggregate CB-CPU points for planned purchase
		375	:total rendering time (in hours) required for indicated workload
		0.87	:% renderfarm utilitzation **Numbers over 1.00 indicate exceeded inhouse capacity
		16666.7	:total monthly frame rendering capacity of proposed new renderfarm (ave.) using indicated current frame complexity
*EXPERIMENTAL SECTION*
enter "1.2" for multithreaded performance gains with HT enabled - otherwise just leave "1"	1.2
enter current average core clock speed (in GHz) of CPUs	2.4
enter average number of cores per node	4
number of cores in current renderfarm
input average core clock speed (in GHz) of new CPUs	2.5
# of new cores availabe		8	total # physical cores
		20.00	# GHz/hr available on proposed farm
		8640.00	total Ghz/hours available on proposed farm
		7500	total Ghz/hours required on proposed

New Hardware costs
cost of each new 10300 module	$6,000.00
cost of additional software for each new module (rendernode)	$0.00
cost of additional items	$0.00
cost for new 10300 renderfarm		$6,000.00
mothly cost on 3 year commercial lease		$199.20
monthly HW cost per frame on animation		$0.08

Cost charged BY customer TO their CLIENT for finished minute of animation
Cost charged BY customer TO their CLIENT for finished second of animation
Cost charged BY customer TO their CLIENT for rendering (per hour)
Cost charged TO studio BY commercial rendefarm service (out of house) for minute of animation

I think some of thw above COST data could come from our data base by referncing the Quote #. Right?? -AG

renderfarm capacity and needs analysis worksheet_v.1.7

Calculator

customer report

formulas