Performance Tuning Tips
From RifidiWiki
- Turn off diagnostic apps (others as well optional as shouldn't have impact unless used as part of apps) -
0:Rifidi App: AppService:ReadZones (STARTED);
1:Rifidi App: AppService:SensorStatus (STARTED);
2:Rifidi App: AppService:UniqueTagInterval (STARTED);
3:Rifidi App: AppService:StableSet (STARTED);
4:Rifidi App: AppService:LimitStableSet (STARTED);
5:Rifidi App: AppService:UniqueTagBatchInterval (START;
6:Rifidi App: AppService:RSSI (STARTED);
7:Rifidi App: Diagnostic:GPIO (STOPPED);
8:Rifidi App: Diagnostic:Serial (STOPPED);
9:Rifidi App: Diagnostic:Tags (STARTED);
10:Rifidi App: Diagnostic:TagGenerator (STARTED);
11:Rifidi App: Monitoring:ReadZones (STARTED);
12:Rifidi App: Monitoring:Tags (STARTED)
13:Rifidi App: Monitoring:SensorStatus (STARTED)
- Consider changing java heap size settings from default 256mb (In eclipse this is limited to 256mb is my understanding)
- 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
- In particular (20.2.13. Tune or disable delivery order guarantees - if event order is not required by application such as in case of work in progress) - considering option to override in 3.1 easier for user
- Esper Configuration - http://esper.codehaus.org/esper-4.2.0/doc/reference/en/html/configuration.html
Package/class where Rifidi invokes Esper Manager - https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/org.rifidi.edge/src/org/rifidi/edge/services/EsperManagementServiceImpl.java
- Best practice - when creating custom esper wrap as a rifidi service (looking to make this easier in 3.1) - link to steps on how to config - http://wiki.rifidi.net/index.php?title=How_to_add_a_new_Rifidi_Service
- 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
