Performance Tuning Tips - Revision history

Bppause: /* Server Tuning */

2014-10-01T19:10:25Z

‎Server Tuning

Manuel transcends: /* Server Tuning */

2014-10-01T19:09:14Z

‎Server Tuning

Bppause: /* Server Tuning */

2014-10-01T19:06:37Z

‎Server Tuning

Bppause: /* Server Tuning */

2014-10-01T19:03:01Z

‎Server Tuning

Bppause: /* Server Tuning */

2014-10-01T19:00:46Z

‎Server Tuning

Bppause: /* Key Factsors to consider */

2014-09-29T16:50:15Z

‎Key Factsors to consider

Bppause at 16:48, 29 September 2014

2014-09-29T16:48:24Z

Bppause at 16:42, 29 September 2014

2014-09-29T16:42:41Z

Bppause at 20:58, 11 August 2014

2014-08-11T20:58:38Z

Bppause at 20:05, 11 August 2014

2014-08-11T20:05:52Z

@@ Line 10: / Line 10: @@
 *How to Turn off Diagnostic:Tags  In server\applications\Diagnostic\Tags.properties set LazyStart=true (default is false) to stop Diagnistic:Tags app from starting by default - recenttags and currenttags commands will no longer function butr this will provide performance/memory improvement as in production mode these commands should not be required
-*How to Turn off Monitoring:Tags  In server\applications\Monitoring\Tags.properties set LazyStart=true (default is false) to stop Monitoring:Tags app from starting by default Note: Tags will no longer be written to default queue to monitor Tag reads by work bench but this provides large performance increase under heavy loads
+*How to Turn off Monitoring:Tags  In server\applications\Monitoring\Tags.properties set LazyStart=true (default is false) (as of 3.1 release) to stop Monitoring:Tags app from starting by default Note: Tags will no longer be written to default queue to monitor Tag reads by work bench but this provides large performance increase under heavy loads
 :Rifidi App: AppService:ReadZones (STARTED);
 :Rifidi App: AppService:SensorStatus (STARTED);

@@ Line 8: / Line 8: @@
 *Turn off diagnostic and monitoring apps in particular 12:Rifidi App: Monitoring:Tags  (others as well optional as shouldn't have impact unless used as part of apps)
-*How to Turn off Diagnostic:Tags  In server\applications\Diagnostic\Tag.properties set LazyStart=true (default is false) to stop Diagnistic:Tags app from starting by default - recenttags and currenttags commands will no longer function butr this will provide performance/memory improvement as in production mode these commands should not be required
+*How to Turn off Diagnostic:Tags  In server\applications\Diagnostic\Tags.properties set LazyStart=true (default is false) to stop Diagnistic:Tags app from starting by default - recenttags and currenttags commands will no longer function butr this will provide performance/memory improvement as in production mode these commands should not be required
-*How to Turn off Monitoring:Tags  In server\applications\Monitoring\Tag.properties set LazyStart=true (default is false) to stop Monitoring:Tags  Note: Tags will no longer be written to default queue to monitir Tag reads by work bench but this provides large performance increase under heavy loads
+*How to Turn off Monitoring:Tags  In server\applications\Monitoring\Tags.properties set LazyStart=true (default is false) to stop Monitoring:Tags app from starting by default Note: Tags will no longer be written to default queue to monitor Tag reads by work bench but this provides large performance increase under heavy loads
 :Rifidi App: AppService:ReadZones (STARTED);
 :Rifidi App: AppService:SensorStatus (STARTED);

@@ Line 10: / Line 10: @@
 *How to Turn off Diagnostic:Tags  In server\applications\Diagnostic\Tag.properties set LazyStart=true (default is false) to stop Diagnistic:Tags app from starting by default - recenttags and currenttags commands will no longer function butr this will provide performance/memory improvement as in production mode these commands should not be required
-*How to Turn off Monitoring:Tags  In server\applications\Diagnostic\Tag.properties set LazyStart=true (default is false) to stop Monitoring:Tags  Note: Tags will no longer be written to default queue to monitir Tag reads by work bench but this provides large performance increase under heavy loads
+*How to Turn off Monitoring:Tags  In server\applications\Monitoring\Tag.properties set LazyStart=true (default is false) to stop Monitoring:Tags  Note: Tags will no longer be written to default queue to monitir Tag reads by work bench but this provides large performance increase under heavy loads
 :Rifidi App: AppService:ReadZones (STARTED);
 :Rifidi App: AppService:SensorStatus (STARTED);

@@ Line 10: / Line 10: @@
 *How to Turn off Diagnostic:Tags  In server\applications\Diagnostic\Tag.properties set LazyStart=true (default is false) to stop Diagnistic:Tags app from starting by default - recenttags and currenttags commands will no longer function butr this will provide performance/memory improvement as in production mode these commands should not be required
-*How to Turn off Monitoring:Tags  Coming Soon - currently need to stop manually
+*How to Turn off Monitoring:Tags  In server\applications\Diagnostic\Tag.properties set LazyStart=true (default is false) to stop Monitoring:Tags  Note: Tags will no longer be written to default queue to monitir Tag reads by work bench but this provides large performance increase under heavy loads
-−
 :Rifidi App: AppService:ReadZones (STARTED);
 :Rifidi App: AppService:SensorStatus (STARTED);

@@ Line 8: / Line 8: @@
 *Turn off diagnostic and monitoring apps in particular 12:Rifidi App: Monitoring:Tags  (others as well optional as shouldn't have impact unless used as part of apps)
-*How to Turn off Diagnostic:Tags  In server\applications\Diagnostic\Tag.properties set LazyStart=false (default is true) to stop Diagnistic:Tags app from starting by default - recenttags and currenttags commands will no longer function butr this will provide performance/memory improvement as in production mode these commands should not be required
+*How to Turn off Diagnostic:Tags  In server\applications\Diagnostic\Tag.properties set LazyStart=true (default is false) to stop Diagnistic:Tags app from starting by default - recenttags and currenttags commands will no longer function butr this will provide performance/memory improvement as in production mode these commands should not be required
 *How to Turn off Monitoring:Tags  Coming Soon - currently need to stop manually
@@ Line 32: / Line 32: @@
 *Consider level of logging - [[Use_org.rifidi.logging]]
 *Turn off console output and run into background - [[Edge_Server_Configuration#Console]]
 ==Esper Tips==
 *Esper Configuration - http://esper.codehaus.org/esper-4.2.0/doc/reference/en/html/configuration.html

@@ Line 1: / Line 1: @@
-==Key Factsors to consider==
+==Key Factors to consider==
-*depends on complexity of sensor events within Rifidi App (how long running, size of event data, frequency etcc.)
+*What is the complexity of sensor events within Rifidi App (how long running, size of event data, frequency etc.)
 *reader adapter performance a. Note: Some reader/sensor adapters perform better than others dependent on vendor adapter native implementation (software and hardware)
-*Size of hardware running rifidi
+*Size of hardware running Rifidi (cpu, memory, storage)
 ==Server Tuning==

← Older revision		Revision as of 16:42, 29 September 2014
Line 31:		Line 31:
	*One can disable bundles in bundles.info (caution if not used by app or required by rifidi core) example bundles one can turn off is mysql, aws bundles if not used by an rifidi app - [[How_to_add_OSGI_Bundles]]		*One can disable bundles in bundles.info (caution if not used by app or required by rifidi core) example bundles one can turn off is mysql, aws bundles if not used by an rifidi app - [[How_to_add_OSGI_Bundles]]
	*Esper Performance Tuning Tips when creating Esper for event processing/tag filtering - http://esper.codehaus.org/esper-4.9.0/doc/reference/en-US/html/performance.html		*Esper Performance Tuning Tips when creating Esper for event processing/tag filtering - http://esper.codehaus.org/esper-4.9.0/doc/reference/en-US/html/performance.html
		+	*Some reader/sensor adapters perform better than others dependent on vendor adapter native implementation (software and hardware)

@@ Line 1: / Line 1: @@
 *Turn off diagnostic and monitoring apps in particular 12:Rifidi App: Monitoring:Tags  (others as well optional as shouldn't have impact unless used as part of apps)
-Note: In server\applications\Diagnostic\Tag.properties set LazyStart=false (default is true) to stop Diagnistic:Tags app from starting by default - recenttags and currenttags commands will no longer function butr this will provide performance/memory improvement as in production mode these commands should not be required
+*How to Turn off Diagnostic:Tags  In server\applications\Diagnostic\Tag.properties set LazyStart=false (default is true) to stop Diagnistic:Tags app from starting by default - recenttags and currenttags commands will no longer function butr this will provide performance/memory improvement as in production mode these commands should not be required
 :Rifidi App: AppService:ReadZones (STARTED);
@@ Line 10: / Line 12: @@
 :Rifidi App: AppService:UniqueTagBatchInterval (START;
 :Rifidi App: AppService:RSSI (STARTED);
-        '''7:Rifidi App: Diagnostic:GPIO (STOPPED);
+:Rifidi App: Diagnostic:GPIO (STOPPED);
 :Rifidi App: Diagnostic:Serial (STOPPED);
 :Rifidi App: Diagnostic:Tags (STARTED);