Comments on: Power Graphing http://knolleary.net/2008/05/05/power-graphing/ taking my thoughts for a walk Sat, 26 Jul 2008 03:01:13 +0000 http://wordpress.org/?v=2.5.1 By: dale lane » Blog Archive » CurrentCost - getting the history into Windows http://knolleary.net/2008/05/05/power-graphing/#comment-11011 dale lane » Blog Archive » CurrentCost - getting the history into Windows Sun, 15 Jun 2008 21:33:21 +0000 http://knolleary.net/?p=157#comment-11011 [...] plan The more geeky amongst us have connected the CurrentCost to a server of some sort. By connecting it to something [...] [...] plan The more geeky amongst us have connected the CurrentCost to a server of some sort. By connecting it to something [...]

]]> By: Effing the Ineffable » Interfacing the CurrentCost meter to your PC http://knolleary.net/2008/05/05/power-graphing/#comment-11010 Effing the Ineffable » Interfacing the CurrentCost meter to your PC Sun, 15 Jun 2008 16:54:06 +0000 http://knolleary.net/?p=157#comment-11010 [...] a simple little gadget that measures power usage in your house. These are being discussed on IBM blogs everywhere, because while the device itself is very neat, it also has the ability to output the [...] [...] a simple little gadget that measures power usage in your house. These are being discussed on IBM blogs everywhere, because while the device itself is very neat, it also has the ability to output the [...]

]]> By: andyp http://knolleary.net/2008/05/05/power-graphing/#comment-10999 andyp Thu, 05 Jun 2008 08:15:35 +0000 http://knolleary.net/?p=157#comment-10999 I have to say that the fact that Google Charts are basically just spitting out PNGs for display makes them far more flexible across a range of devices anyway. Opera Mini on my BlackBerry can cope with that, for instance :-) I have to say that the fact that Google Charts are basically just spitting out PNGs for display makes them far more flexible across a range of devices anyway. Opera Mini on my BlackBerry can cope with that, for instance :-)

]]> By: nick http://knolleary.net/2008/05/05/power-graphing/#comment-10998 nick Thu, 05 Jun 2008 07:33:31 +0000 http://knolleary.net/?p=157#comment-10998 @abu21, True, Moonlight is being worked on by the guys at Novell. Once they get something released that I can easily install, then I may take a look. Certainly the fact they plan for a proper SDK on linux will be an advantage over Flash. In the mean time, I'll stick to my open standards. @abu21,

True, Moonlight is being worked on by the guys at Novell. Once they get something released that I can easily install, then I may take a look.

Certainly the fact they plan for a proper SDK on linux will be an advantage over Flash.

In the mean time, I’ll stick to my open standards.

]]> By: abu21 http://knolleary.net/2008/05/05/power-graphing/#comment-10997 abu21 Thu, 05 Jun 2008 06:56:24 +0000 http://knolleary.net/?p=157#comment-10997 hey nick, visifire is under GPL, what else can one ask for. regarding silverlight, microsoft is dieing to make it reach every one. currently silverlight supports win & mac. linux will follow soon ( some thing called moonlight) hey nick,
visifire is under GPL, what else can one ask for.
regarding silverlight, microsoft is dieing to make it reach every one. currently silverlight supports win & mac. linux will follow soon ( some thing called moonlight)

]]> By: nick http://knolleary.net/2008/05/05/power-graphing/#comment-10988 nick Wed, 04 Jun 2008 13:10:40 +0000 http://knolleary.net/?p=157#comment-10988 abu21, thanks for the comment. I would question how a completely proprietary technology that only works on Windows would improve the quality of these graphs. abu21, thanks for the comment.

I would question how a completely proprietary technology that only works on Windows would improve the quality of these graphs.

]]> By: abu21 http://knolleary.net/2008/05/05/power-graphing/#comment-10986 abu21 Wed, 04 Jun 2008 10:28:26 +0000 http://knolleary.net/?p=157#comment-10986 hey, Chk this out visifire, i think it can improve the quality of your charts coz it is powered by silverlight hey,
Chk this out visifire, i think it can improve the quality of your charts coz it is powered by silverlight

]]> By: dale lane » Blog Archive » Accessing MySQL from Perl on SlugOS http://knolleary.net/2008/05/05/power-graphing/#comment-10943 dale lane » Blog Archive » Accessing MySQL from Perl on SlugOS Tue, 27 May 2008 14:52:52 +0000 http://knolleary.net/?p=157#comment-10943 [...] I decided to make a start on collecting the data. My plan was to copy what Nick had done and create a MySQL database to store the info, with a table to store a timestamp and the watt [...] [...] I decided to make a start on collecting the data. My plan was to copy what Nick had done and create a MySQL database to store the info, with a table to store a timestamp and the watt [...]

]]> By: Dale Lane http://knolleary.net/2008/05/05/power-graphing/#comment-10942 Dale Lane Tue, 27 May 2008 14:07:37 +0000 http://knolleary.net/?p=157#comment-10942 RE: I’ll have to keep an eye on this to make sure it doesn’t run away with my free disk space. I'm using a similar MySQL DB structure to you (naturally, since I nicked your scripts to get me started ;-) ), and have been checking the size it takes. On my NSLU-2, each update requires 9 bytes. A few rough back-of-the-envelope calculations: Assume we store an update every 6 seconds - each needing 9 bytes of storage. 1 day == 24 hours == 24 * 60 minutes == 24 * 60 * 60 seconds == (24 * 60 * 60) / 6 updates So that is 14400 updates in a day - requiring 129600 bytes of storage Multiply that by 365, and we need approx. 45 MB (47304000 bytes) for a full year's data. Think it'll be a while before this starts being a problem :-) RE: I’ll have to keep an eye on this to make sure it doesn’t run away with my free disk space.

I’m using a similar MySQL DB structure to you (naturally, since I nicked your scripts to get me started ;-) ), and have been checking the size it takes.

On my NSLU-2, each update requires 9 bytes.

A few rough back-of-the-envelope calculations:

Assume we store an update every 6 seconds - each needing 9 bytes of storage.

1 day == 24 hours
== 24 * 60 minutes
== 24 * 60 * 60 seconds
== (24 * 60 * 60) / 6 updates

So that is 14400 updates in a day - requiring 129600 bytes of storage

Multiply that by 365, and we need approx. 45 MB (47304000 bytes) for a full year’s data.

Think it’ll be a while before this starts being a problem :-)

]]> By: CurrentCost « log.illsley.org http://knolleary.net/2008/05/05/power-graphing/#comment-10941 CurrentCost « log.illsley.org Mon, 26 May 2008 12:17:17 +0000 http://knolleary.net/?p=157#comment-10941 [...] are lots of interesting things to do with the data, which I’ll start to play with once I have a [...] [...] are lots of interesting things to do with the data, which I’ll start to play with once I have a [...]

]]>