Notification Actions Engine - Revision history

Tobias: /* Limitations of the service */

2016-01-29T13:06:49Z

‎Limitations of the service

Tobias: /* Limitations of the service */

2016-01-29T13:06:29Z

‎Limitations of the service

Tobias: /* Limitations of the service */

2016-01-29T13:05:02Z

‎Limitations of the service

Tobias: /* Piwik Accounts */

2016-01-29T12:21:28Z

‎Piwik Accounts

Tobias: /* Piwik Accounts */

2016-01-29T12:20:37Z

‎Piwik Accounts

Tobias: /* Piwik Accounts */

2016-01-29T12:19:35Z

‎Piwik Accounts

Tobias at 16:12, 28 January 2016

2016-01-28T16:12:37Z

Tobias at 15:33, 28 January 2016

2016-01-28T15:33:40Z

Tobias at 15:32, 28 January 2016

2016-01-28T15:32:26Z

Tobias: /* Other */

2016-01-18T17:13:30Z

‎Other

@@ Line 208: / Line 208: @@
 ; With which parameters does the service scale?
 {{comment|How many concurrent E-Shops, how many concurrent products and how many users/E-Shop customers are possible without causing loss in quality/speed for the hardware described above?}}
-: In order to analise the visitor behaviour the engine needs to receive click events from Piwik ([[E-Compass Piwik Plugin]]). For the case that Piwik is connected to our Apache Server and uses SLL ([https://e-compass.iao.fraunhofer.de/processengine/ '''https'''://e-compass.iao.fraunhofer.de/processengine/]), load tests showed that the Engine is able to receive up to 200 click events/sec with an avg. processing time < 0.5 sec and a max. < 5 sec. If you connect to the Jetty Server directly ([https://e-compass.iao.fraunhofer.de:8080/processengine/ https://e-compass.iao.fraunhofer.de''':8080'''/processengine/]) the Engine is able to receive up to 300 click events/sec with an avg. processing time < 0.1 sec and a max. < 1 sec (300 click events/sec correspond to 1,200 new shop visitor per sec, staying 1 min and doing 15 clicks). The limit is about 360 click events/sec which can cause processing times above 10 sec (10sec is the maximum time for a voucher to work properly).
+: In order to analise the visitor behaviour the engine needs to receive click events from Piwik ([[E-Compass Piwik Plugin]]). For the case that Piwik is connected to our Apache Server and uses SLL ([https://e-compass.iao.fraunhofer.de/processengine/ '''https'''://e-compass.iao.fraunhofer.de/processengine/]), load tests showed that the Engine is able to receive up to 200 click events/sec with an avg. processing time < 0.5 sec and a max. < 5 sec. If you connect to the Jetty Server directly ([http://e-compass.iao.fraunhofer.de:8080/processengine/ https://e-compass.iao.fraunhofer.de''':8080'''/processengine/]) the Engine is able to receive up to 300 click events/sec with an avg. processing time < 0.1 sec and a max. < 1 sec (300 click events/sec correspond to 1,200 new shop visitor per sec, staying 1 min and doing 15 clicks). The limit is about 360 click events/sec which can cause processing times above 10 sec (10sec is the maximum time for a voucher to work properly).
 : Parameters relevant for the scaling of this module are the overall number of users of all E-Shops and the number of rules. Each rule generates one request every ten minutes, i.e. the rules are checked every ten minutes. Each request takes 100 - 200 ms of time. So in ten minutes a maximum of 3000 request should be possible without further parallelization. There is one special kind of rule, which is the voucher rule (i.e. if a user shows a certain behaviour on the E-Shop a voucher is shown to him). This rule generates traffic depending on user behaviour, which means that this is not predictable. Therefore the above estimate can only give an orientation, not a guaranteed limit and one should always keep reserves for situations in which many users (over all E-Shops) show a behaviour that triggers a voucher rule.
 ; If higher scaling was wanted, which of the hardware parameters would need to be increased?

@@ Line 208: / Line 208: @@
 ; With which parameters does the service scale?
 {{comment|How many concurrent E-Shops, how many concurrent products and how many users/E-Shop customers are possible without causing loss in quality/speed for the hardware described above?}}
-: In order to analise the visitor behaviour the engine needs to receive click events from Piwik ([[E-Compass Piwik Plugin]]). For the case that Piwik is connected to our Apache Server and uses SLL ('''https'''://e-compass.iao.fraunhofer.de/processengine/), load tests showed that the Engine is able to receive up to 200 click events/sec with an avg. processing time < 0.5 sec and a max. < 5 sec. If you connect to the Jetty Server directly (https://e-compass.iao.fraunhofer.de''':8080'''/processengine/) the Engine is able to receive up to 300 click events/sec with an avg. processing time < 0.1 sec and a max. < 1 sec (300 click events/sec correspond to 1,200 new shop visitor per sec, staying 1 min and doing 15 clicks). The limit is about 360 click events/sec which can cause processing times above 10 sec (10sec is the maximum time for a voucher to work properly).
+: In order to analise the visitor behaviour the engine needs to receive click events from Piwik ([[E-Compass Piwik Plugin]]). For the case that Piwik is connected to our Apache Server and uses SLL ([https://e-compass.iao.fraunhofer.de/processengine/ '''https'''://e-compass.iao.fraunhofer.de/processengine/]), load tests showed that the Engine is able to receive up to 200 click events/sec with an avg. processing time < 0.5 sec and a max. < 5 sec. If you connect to the Jetty Server directly ([https://e-compass.iao.fraunhofer.de:8080/processengine/ https://e-compass.iao.fraunhofer.de''':8080'''/processengine/]) the Engine is able to receive up to 300 click events/sec with an avg. processing time < 0.1 sec and a max. < 1 sec (300 click events/sec correspond to 1,200 new shop visitor per sec, staying 1 min and doing 15 clicks). The limit is about 360 click events/sec which can cause processing times above 10 sec (10sec is the maximum time for a voucher to work properly).
 : Parameters relevant for the scaling of this module are the overall number of users of all E-Shops and the number of rules. Each rule generates one request every ten minutes, i.e. the rules are checked every ten minutes. Each request takes 100 - 200 ms of time. So in ten minutes a maximum of 3000 request should be possible without further parallelization. There is one special kind of rule, which is the voucher rule (i.e. if a user shows a certain behaviour on the E-Shop a voucher is shown to him). This rule generates traffic depending on user behaviour, which means that this is not predictable. Therefore the above estimate can only give an orientation, not a guaranteed limit and one should always keep reserves for situations in which many users (over all E-Shops) show a behaviour that triggers a voucher rule.
 ; If higher scaling was wanted, which of the hardware parameters would need to be increased?

@@ Line 208: / Line 208: @@
 ; With which parameters does the service scale?
 {{comment|How many concurrent E-Shops, how many concurrent products and how many users/E-Shop customers are possible without causing loss in quality/speed for the hardware described above?}}
 : Parameters relevant for the scaling of this module are the overall number of users of all E-Shops and the number of rules. Each rule generates one request every ten minutes, i.e. the rules are checked every ten minutes. Each request takes 100 - 200 ms of time. So in ten minutes a maximum of 3000 request should be possible without further parallelization. There is one special kind of rule, which is the voucher rule (i.e. if a user shows a certain behaviour on the E-Shop a voucher is shown to him). This rule generates traffic depending on user behaviour, which means that this is not predictable. Therefore the above estimate can only give an orientation, not a guaranteed limit and one should always keep reserves for situations in which many users (over all E-Shops) show a behaviour that triggers a voucher rule.
 ; If higher scaling was wanted, which of the hardware parameters would need to be increased?

@@ Line 202: / Line 202: @@
 | piwikTrackerLocationUrl||URL to the Piwik installation of the e-shop owner ||www.my-shop.com/piwik
 |-
-| piwikAuthToken||The Piwik auth_token of the e-shop owner's account ||f02c12u37dc0wu781uekd3nm64hfu38d3
+| piwikAuthToken||The Piwik auth_token of the e-shop owner's account ||0123456789abcdef0123456789abcdef
 |}

@@ Line 138: / Line 138: @@
 http://e-compass.iao.fraunhofer.de/processengine/createNewPiwikSite.do
 <br/><br/>
-For creating an e-Shop and account on the UMA Piwik:
+For creating an e-Shop and an account on the Piwik of the [[Data Collector Consolidator]]:
 <br/> (With example values)
 {| class="wikitable"

@@ Line 164: / Line 164: @@
 | userPiwikSiteId||Is generated once the e-shop is created ||''left blank''
 |-
-| piwikTrackerLocationUrl||Uses the URL of the UMA Piwik as default ||''left blank''
+| piwikTrackerLocationUrl||Uses the URL of the Piwik of the [[Data Collector Consolidator]] as default ||''left blank''
 |-
-| piwikAuthToken||Uses the admin auth_token of the UMA Piwik as default ||''left blank''
+| piwikAuthToken||Uses the admin auth_token of the Piwik of the [[Data Collector Consolidator]] as default ||''left blank''
 |}

← Older revision		Revision as of 16:12, 28 January 2016
Line 1:		Line 1:
−	~~[[Slides_for_script_edit.wmv]]~~
−	~~[[File:Slides for script edit.wmv\|thumbnail\|Film]]~~
−
−	~~[[File:Slides for script edit.wmv\|framed\|Film2]]~~
−	~~[[Media:Slides_for_script_edit.wmv]]~~
−
	{{Hardware \| text =		{{Hardware \| text =
	\| model = Cisco UCS B200 M4 und M2 / Cisco UCS B230 M2		\| model = Cisco UCS B200 M4 und M2 / Cisco UCS B230 M2

← Older revision		Revision as of 15:33, 28 January 2016
Line 1:		Line 1:
	[[Slides_for_script_edit.wmv]]		[[Slides_for_script_edit.wmv]]
		+	[[File:Slides for script edit.wmv\|thumbnail\|Film]]

		+	[[File:Slides for script edit.wmv\|framed\|Film2]]
	[[Media:Slides_for_script_edit.wmv]]		[[Media:Slides_for_script_edit.wmv]]

← Older revision		Revision as of 15:32, 28 January 2016
Line 1:		Line 1:
		+	[[Slides_for_script_edit.wmv]]
		+
		+	[[Media:Slides_for_script_edit.wmv]]
		+
	{{Hardware \| text =		{{Hardware \| text =
	\| model = Cisco UCS B200 M4 und M2 / Cisco UCS B230 M2		\| model = Cisco UCS B200 M4 und M2 / Cisco UCS B230 M2

@@ Line 130: / Line 130: @@
 === Other ===
 The Notification & Actions Engine needs data about the visitors visiting an E-Shops web page. Therefore the Shop has to use Piwik Analytics with the E-Compass Piwik Plugin installed (Read the [[E-Compass Piwik Plugin]] wiki page for more information).<br /><br/>
 E-shop sites in Piwik which have already been created manually need their belonging Piwik accounts to be created manually later. Newly created e-shops can be created together with their corresponding accounts through following RESTful POST-Request:<br/>
 http://e-compass.iao.fraunhofer.de/processengine/createNewPiwikSite.do