Basic Benchmark - Revision history

Olibouban at 18:43, 9 December 2016

2016-12-09T18:43:29Z

← Older revision		Revision as of 18:43, 9 December 2016
Line 1:		Line 1:
	== Benchmark Setup ==		== Benchmark Setup ==
	The benchmark is to identify a unit of scanning for a project. That unit is based on the following specifications and ~~<b>~~API~~</b> is used~~ to execute the scan to measure the operations precisely:		The benchmark is to identify a unit of scanning for a project. That unit is based on the following specifications and the benchmark program calls the Globalyzer API to execute the scan to measure the operations precisely:
	* 100 files		* 100 files
	* 10,000 lines of code		* 10,000 lines of code

Olibouban at 18:42, 9 December 2016

2016-12-09T18:42:35Z

← Older revision		Revision as of 18:42, 9 December 2016
Line 1:		Line 1:
	== ~~Rationale ==~~		== Benchmark Setup ==

	~~== Logic of the~~ Benchmark ==
	The benchmark is to identify a unit of scanning for a project. That unit is based on the following specifications and <b>API</b> is used to execute the scan to measure the operations precisely:		The benchmark is to identify a unit of scanning for a project. That unit is based on the following specifications and <b>API</b> is used to execute the scan to measure the operations precisely:
	* 100 files		* 100 files

Olibouban: /* Benchmark Results */

2016-12-09T18:42:06Z

Benchmark Results

← Older revision		Revision as of 18:42, 9 December 2016
Line 30:		Line 30:
	== Benchmark Results ==		== Benchmark Results ==

	<~~code~~> Execute Java Scan Benchmark (10K lines of code, 100 files):		<pre>
	Reloaded rule sets		Execute Java Scan Benchmark (10K lines of code, 100 files):
	Executing java scan(1): 11231 milliseconds		Reloaded rule sets
			Executing java scan(1): 11231 milliseconds
	Executing java scan(2): 1140 milliseconds		Executing java scan(2): 1140 milliseconds
	Executing java scan(3): 800 milliseconds		Executing java scan(3): 800 milliseconds
Line 42:		Line 43:
	Executing java scan(9): 576 milliseconds		Executing java scan(9): 576 milliseconds
	Executing java scan(10): 580 milliseconds		Executing java scan(10): 580 milliseconds

	Reloaded rule sets		Reloaded rule sets
	Executing java scan(1): 1377 milliseconds		Executing java scan(1): 1377 milliseconds
Line 53:		Line 55:
	Executing java scan(9): 592 milliseconds		Executing java scan(9): 592 milliseconds
	Executing java scan(10): 576 milliseconds		Executing java scan(10): 576 milliseconds

	Reloaded rule sets		Reloaded rule sets
	Executing java scan(1): 1361 milliseconds		Executing java scan(1): 1361 milliseconds
Line 64:		Line 67:
	Executing java scan(9): 592 milliseconds		Executing java scan(9): 592 milliseconds
	Executing java scan(10): 576 milliseconds		Executing java scan(10): 576 milliseconds
	<~~code~~>		</pre>

Olibouban: /* Benchmark Results */

2016-12-09T18:41:21Z

Benchmark Results

← Older revision		Revision as of 18:41, 9 December 2016
Line 29:		Line 29:

	== Benchmark Results ==		== Benchmark Results ==
	<code>
	Execute Java Scan Benchmark (10K lines of code, 100 files):		<code> Execute Java Scan Benchmark (10K lines of code, 100 files):
	Reloaded rule sets		Reloaded rule sets
	Executing java scan(1): 11231 milliseconds		Executing java scan(1): 11231 milliseconds

Olibouban: /* Benchmark Results */

2016-12-09T18:41:08Z

Benchmark Results

← Older revision		Revision as of 18:41, 9 December 2016
Line 30:		Line 30:
	== Benchmark Results ==		== Benchmark Results ==
	<code>		<code>
	Execute Java Scan Benchmark (10K lines of code, 100 files):		Execute Java Scan Benchmark (10K lines of code, 100 files):
	Reloaded rule sets		Reloaded rule sets
	Executing java scan(1): 11231 milliseconds		Executing java scan(1): 11231 milliseconds
	Executing java scan(2): 1140 milliseconds		Executing java scan(2): 1140 milliseconds
	Executing java scan(3): 800 milliseconds		Executing java scan(3): 800 milliseconds

Olibouban: /* Benchmark Results */

2016-12-09T18:40:54Z

Benchmark Results

← Older revision		Revision as of 18:40, 9 December 2016
Line 29:		Line 29:

	== Benchmark Results ==		== Benchmark Results ==
			<code>
			Execute Java Scan Benchmark (10K lines of code, 100 files):
			Reloaded rule sets
			Executing java scan(1): 11231 milliseconds
			Executing java scan(2): 1140 milliseconds
			Executing java scan(3): 800 milliseconds
			Executing java scan(4): 736 milliseconds
			Executing java scan(5): 768 milliseconds
			Executing java scan(6): 656 milliseconds
			Executing java scan(7): 624 milliseconds
			Executing java scan(8): 587 milliseconds
			Executing java scan(9): 576 milliseconds
			Executing java scan(10): 580 milliseconds
			Reloaded rule sets
			Executing java scan(1): 1377 milliseconds
			Executing java scan(2): 589 milliseconds
			Executing java scan(3): 595 milliseconds
			Executing java scan(4): 640 milliseconds
			Executing java scan(5): 592 milliseconds
			Executing java scan(6): 560 milliseconds
			Executing java scan(7): 576 milliseconds
			Executing java scan(8): 576 milliseconds
			Executing java scan(9): 592 milliseconds
			Executing java scan(10): 576 milliseconds
			Reloaded rule sets
			Executing java scan(1): 1361 milliseconds
			Executing java scan(2): 576 milliseconds
			Executing java scan(3): 592 milliseconds
			Executing java scan(4): 544 milliseconds
			Executing java scan(5): 576 milliseconds
			Executing java scan(6): 574 milliseconds
			Executing java scan(7): 577 milliseconds
			Executing java scan(8): 577 milliseconds
			Executing java scan(9): 592 milliseconds
			Executing java scan(10): 576 milliseconds
			<code>

Olibouban: /* Logic of the Benchmark */

2016-12-09T18:39:49Z

Logic of the Benchmark

← Older revision		Revision as of 18:39, 9 December 2016
Line 2:		Line 2:

	== Logic of the Benchmark ==		== Logic of the Benchmark ==
	The benchmark is to identify a unit of scanning for a project. That unit is based on the following specifications and <b>~~Lite~~</b> is used to execute the scan:		The benchmark is to identify a unit of scanning for a project. That unit is based on the following specifications and <b>API</b> is used to execute the scan to measure the operations precisely:
	* 100 files		* 100 files
	* 10,000 lines of code		* 10,000 lines of code
	* The default Java rule set		* The default Java rule set
			* 10 scans are run in one batch.
	* 10 scans are run.
	** The first time the scan is executed, the Java rule set is loaded		** The first time the scan is executed, the Java rule set is loaded
	** the next 9 runs do not need to load the Java rule set and hence perform better.		** the next 9 runs do not need to load the Java rule set and hence perform better.
			* 3 batches of 10 scans each are run
			** On the first batch, the system must connect to Globalyzer, get the meta-data, etc., which lowers the performance
			** On the subsequent batches, the connection is established, and the first scan only reloads the rule sets as mentioned above.

	If you have, say, 100,000 lines of code, on the system specified, it would about take 10 times the duration of this test.		If you have, say, 100,000 lines of code, on the system specified, it would about take 10 times the duration of this test.

Olibouban: /* Logic of the Benchmark */

2016-12-09T18:37:01Z

Logic of the Benchmark

← Older revision		Revision as of 18:37, 9 December 2016
Line 6:		Line 6:
	* 10,000 lines of code		* 10,000 lines of code
	* The default Java rule set		* The default Java rule set

			* 10 scans are run.
			** The first time the scan is executed, the Java rule set is loaded
			** the next 9 runs do not need to load the Java rule set and hence perform better.

	If you have, say, 100,000 lines of code, on the system specified, it would about take 10 times the duration of this test.		If you have, say, 100,000 lines of code, on the system specified, it would about take 10 times the duration of this test.

Olibouban: /* Logic of the Benchmark */

2016-12-09T18:33:26Z

Logic of the Benchmark

← Older revision		Revision as of 18:33, 9 December 2016
Line 2:		Line 2:

	== Logic of the Benchmark ==		== Logic of the Benchmark ==
	The benchmark is to identify a unit of scanning for a project. That unit is based on the following specifications:		The benchmark is to identify a unit of scanning for a project. That unit is based on the following specifications and <b>Lite</b> is used to execute the scan:
	* 100 files		* 100 files
	* 10,000 lines of code		* 10,000 lines of code
	* The default Java rule set		* The default Java rule set

	~~The benchmark is carried out using Lite.~~

	If you have, say, 100,000 lines of code, on the system specified, it would about take 10 times the duration of this test.		If you have, say, 100,000 lines of code, on the system specified, it would about take 10 times the duration of this test.

Olibouban: /* Logic of the Benchmark */

2016-12-09T18:32:35Z

Logic of the Benchmark

← Older revision		Revision as of 18:32, 9 December 2016
Line 7:		Line 7:
	* The default Java rule set		* The default Java rule set

			The benchmark is carried out using Lite.

	If you have, say, 100,000 lines of code, on the system specified, it would about take 10 times the duration of this test.		If you have, say, 100,000 lines of code, on the system specified, it would about take 10 times the duration of this test.

	If you have, say, two rule sets, it would take about twice the duration of this test.		If you have, say, two rule sets, it would take about twice the duration of this test.