8.0.4

• Removed update 0002 from update_class.php as it is depreciated
• Addition of method that returns write and read apikey when login is provided

8.0.3 Bug fixes

• consistent dial and feed value decimal place format
• corrected realtime time window for 1 and 5 min window

8.0.2 Bug fixes

• Dial and list interface share same decimal point formatting
• Fixed bug in node model that was setting scale to zero
• Fixed abs bug in visualisation stats
• Fixed multiigraph save bug (needed encodeURIcomponent)

v8.0

See forum posts linked for details on most of the new features:
Debianization: http://openenergymonitor.org/emon/node/4067
New feed engine's, nodes interface: http://openenergymonitor.org/emon/node/3868
Emoncms development log March 2014 http://openenergymonitor.org/emon/node/4008
Development: Calculating Wh totals on the emontx http://openenergymonitor.org/emon/node/3995

this corresponds to apt package version 8.0-1

Merge pull request #162 from Dave-McCraw/debian-packaging

Debian packaging

v7.0 Redis

As part of recent work to improve the performance of emoncms because of high load's on emoncms.org redis was introduced to store feed and input meta data including last feed time and value fields which where causing significant write load on the server. This change benefits all installation types of emoncms whether emoncms.org or a raspberrypi as it siginficantly reduces the amount of disk writes.

Using redis in this way leads to quite a big performance improvement. Enabling almost 5 times the request rate in benchmarking.

Blog post: http://openenergymonitor.blogspot.co.uk/2013/11/improving-emoncms-performance-with_8.html

To upgrade you will need redis server installed and the phpredis client:

sudo apt-get install redis-server
sudo pecl install redis

V6.9 Pre-redis release

Last state of emoncms master before merge of redis meta data branch. Use this branch if you wish to use emoncms with all changes up to the addition of redis.

v6.0 timestore

v6 (timestore+)

Emoncms version 6 brings in the capability of a new feed storage engine called timestore. Timestore is time-series database designed specifically for time-series data developed by Mike Stirling.

mikestirling.co.uk/redmine/projects/timestore

Timestore's advantages:

Faster Query speeds With timestore feed data query requests are about 10x faster (2700ms using mysql vs 210ms using timestore). Note: initial benchmarks show timestore request time to be around 45ms need to investigate the slightly slower performance may be on the emoncms end rather than timestore.

Reduced Disk use Disk use is also much smaller, A test feed stored in an indexed mysql table used 170mb, stored using timestore which does not need an index and is based on a fixed time interval the same feed used 42mb of disk space.

In-built averaging Timestore also has an additional benefit of using averaged layers which ensures that requested data is representative of the window of time each datapoint covers.