NU32v2: Benchmark Test - Revision history

Lynch at 11:29, 16 January 2016

2016-01-16T11:29:43Z

← Older revision		Revision as of 06:29, 16 January 2016
Line 1:		Line 1:
			'''THIS PAGE REFERS TO A PRE-RELEASE VERSION OF THE NU32 PIC32 DEVELOPMENT BOARD. FOR INFORMATION, SAMPLE CODE, AND VIDEOS RELATED TO THE PRODUCTION VERSION (2016 AND LATER), AND TO THE CORRESPONDING BOOK "EMBEDDED COMPUTING AND MECHATRONICS WITH THE PIC32 MICROCONTROLLER," VISIT [[NU32\|THE NU32 PAGE]].'''
	'''* UNDER CONSTRUCTION *'''


	Benchmarking is a useful tool in testing how fast a processor can run. With the PIC32, we are primarily interested in seeing how fast its CPU can perform mathematical operations.		Benchmarking is a useful tool in testing how fast a processor can run. With the PIC32, we are primarily interested in seeing how fast its CPU can perform mathematical operations.

Nelson Rosa: NU32v2: NU32v2 Benchmark Test moved to NU32v2: Benchmark Test: redundant usage of NU32v2

2011-02-21T18:06:41Z

NU32v2: NU32v2 Benchmark Test moved to NU32v2: Benchmark Test: redundant usage of NU32v2

← Older revision	Revision as of 13:06, 21 February 2011
(No difference)

Nelson Rosa: /* Details */

2011-02-21T17:41:21Z

Details

← Older revision		Revision as of 12:41, 21 February 2011
Line 13:		Line 13:

	== Details ==		== Details ==
	The common arithmetic operators, multiplication (*), division(/), addition (+), and subtraction (-) were tested on the PIC32. Because timing results can vary depending on which C data type (char, short, int, long long, float, and double) is used, the final table includes the number of cycles a particular operator and data type pair took to compute. The table below is taken from a student who took ME 333 in the Winter 2011 term. The values are representative of what the class got as a whole.		The common arithmetic operators, multiplication (*), division(/), addition (+), and subtraction (-) were tested on the PIC32. Because timing results can vary depending on which C data type (char, short, int, long long, float, and double) is used, the final table includes the number of cycles a particular operator and data type pair took to compute. The table below is taken from a student who took ME 333 in the Winter 2011 term. The values, in cycles, are representative of what the class got as a whole.

	{\| border="1" align="center" style="text-align:center;"		{\| border="1" align="center" style="text-align:center;"
Line 57:		Line 57:
	\|}		\|}

	A small subset of the built-in mathematical functions defined in <math.h> were also tested.		A small subset of the built-in mathematical functions defined in <math.h> were also tested. The values, as in the previous table, are in cycles.

	{\| border="1" align="center" style="text-align:center;"		{\| border="1" align="center" style="text-align:center;"

Nelson Rosa: /* Details */

2011-02-21T17:40:10Z

Details

← Older revision		Revision as of 12:40, 21 February 2011
Line 57:		Line 57:
	\|}		\|}

		⚫	A small subset of the built-in mathematical functions defined in <math.h> were also tested.

			{\| border="1" align="center" style="text-align:center;"

			\|sinf
⚫	A small subset of the built-in mathematical functions defined in <math.h> were also tested.
			\|263
			\|-
			\|sin
			\|647
			\|-
			\|sqrtf
			\|293
			\|-
			\|sqrt
			\|603
			\|}

	== Library Functions ==		== Library Functions ==

Nelson Rosa: /* Overview */

2011-02-21T17:33:04Z

Overview

← Older revision		Revision as of 12:33, 21 February 2011
Line 4:		Line 4:

	== Overview ==		== Overview ==

			Add high-level overview of CPU, including:


			* The processor executes instructions in an assembly line fashion similar to how cars are assembled. In any given clock cycle, the processor could be executing several instructions at once (each instruction occupying a different stage in the assembly line of course). One issue that commonly arises is when assembly instruction $i$ needs the result of instruction $i-1$ (where $i-1$ is one stage ahead of $i$), but the processor has not yet finished computing the result of $i-1$. Unfortunately, the processor has no choice but to stall instruction $i$ until the value for $i-1$ becomes available. Your timing results will include both the time to execute an instruction and any processor stalls.
			* One clock cycle is 1/SYSFREQ and as instructions pass through the processor's ``assembly line'' at 80MHz, the processor is eventually able to complete one instruction every 12.5ns. Therefore, for all intensive purposes, you can pretend that one line of computer assembly code takes one cycle to compelete.
			* The PIC has no hardware to compute floating-point operations. This piece of hardware is known as a floating point unit or FPU. The calculations are instead performed in software.

	== Details ==		== Details ==

Nelson Rosa: /* Details */

2011-02-21T17:30:29Z

Details

← Older revision		Revision as of 12:30, 21 February 2011
Line 6:		Line 6:

	== Details ==		== Details ==
	The common arithmetic operators, multiplication (*), division(/), addition (+), and subtraction (-) were tested on the PIC32. Because timing results can vary depending on which C data type (char, short, int, long long, float, and double) is used, the final table includes the number of cycles a particular operator and data type pair took to compute.		The common arithmetic operators, multiplication (*), division(/), addition (+), and subtraction (-) were tested on the PIC32. Because timing results can vary depending on which C data type (char, short, int, long long, float, and double) is used, the final table includes the number of cycles a particular operator and data type pair took to compute. The table below is taken from a student who took ME 333 in the Winter 2011 term. The values are representative of what the class got as a whole.

	{\| border="1" align="center" style="text-align:center;"		{\| border="1" align="center" style="text-align:center;"

Nelson Rosa: /* Details */

2011-02-21T17:28:57Z

Details

← Older revision		Revision as of 12:28, 21 February 2011
Line 23:		Line 23:
	\|12		\|12
	\|68		\|68
	\|~~101~~		\|102
	\|-		\|-
	\|sub (-)		\|sub (-)
Line 31:		Line 31:
	\|10		\|10
	\|79		\|79
	\|~~125~~		\|123
	\|-		\|-
	\|mult (*)		\|mult (*)
Line 45:		Line 45:
	\|16		\|16
	\|16		\|16
	\|~~120~~		\|119
	\|149		\|149
	\|~~312~~		\|314
	\|}		\|}

Nelson Rosa: /* Details */

2011-02-21T17:26:30Z

Details

@@ Line 26: / Line 26: @@
 |-
 |sub (-)
 |5
 |5
@@ Line 31: / Line 32: @@
 |79
 |125
 |}

Nelson Rosa: /* Details */

2011-02-21T17:24:58Z

Details

← Older revision		Revision as of 12:24, 21 February 2011
Line 7:		Line 7:
	== Details ==		== Details ==
	The common arithmetic operators, multiplication (*), division(/), addition (+), and subtraction (-) were tested on the PIC32. Because timing results can vary depending on which C data type (char, short, int, long long, float, and double) is used, the final table includes the number of cycles a particular operator and data type pair took to compute.		The common arithmetic operators, multiplication (*), division(/), addition (+), and subtraction (-) were tested on the PIC32. Because timing results can vary depending on which C data type (char, short, int, long long, float, and double) is used, the final table includes the number of cycles a particular operator and data type pair took to compute.

			{\| border="1" align="center" style="text-align:center;"
			\|
			\|char
			\|short
			\|int
			\|long long
			\|float
			\|double
			\|-
			\|add (+)
			\|5
			\|5
			\|5
			\|12
			\|68
			\|101
			\|-
			\|sub (-)
			\|5
			\|5
			\|10
			\|79
			\|125
			\|}

Nelson Rosa: /* Details */

2011-02-21T17:18:08Z

Details

← Older revision		Revision as of 12:18, 21 February 2011
Line 6:		Line 6:

	== Details ==		== Details ==
			The common arithmetic operators, multiplication (*), division(/), addition (+), and subtraction (-) were tested on the PIC32. Because timing results can vary depending on which C data type (char, short, int, long long, float, and double) is used, the final table includes the number of cycles a particular operator and data type pair took to compute.


			A small subset of the built-in mathematical functions defined in <math.h> were also tested.

	== Library Functions ==		== Library Functions ==