Author Topic: Success rate for google PM or 3rd party products  (Read 4630 times)

scottf200

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Success rate for google PM or 3rd party products
« on: July 21, 2011, 07:29:05 AM »
Ted500 r452 gateway firmware:
Iím only getting 16% success rate talking to a 3rd party products server (58/349).  That seems very very low to me.
Going to Google PM is 61% (90/147).

On my TED500 21 MTU I had gateway firmware r383 and it seemed solid for Google PM usage.  With them going away I investigated a few others.  They all said to get gateway firmware r406. After that my success rate for 3rd parties AND Google PM was like 1 or 2% and then it seemed to stop.  I am using the beta r452 now and am havine what I would consider modest to poor success.  See 1st paragraph.

So in general what is the expected success rate (%)?  Is 100% obtainable even?

This does not seem to be a 3rd party problem although I've see 1000 come back on the /stats.htm page as a result (socket).


« Last Edit: July 21, 2011, 07:30:59 AM by scottf200 »

TedDev

  • TED Software Developent
  • Administrator
  • Full Member
  • *****
  • Posts: 158
  • Karma: +0/-0
Re: Success rate for google PM or 3rd party products
« Reply #1 on: July 21, 2011, 06:17:10 PM »
Close to 100% is typical. If you are having problems w/ both PowerMeter and other 3rd party apps, then the issue is most-likely a network issue. The "1000" message means that the gateway is not able to make a socket connection to the remote host. This could either be from the network path being unavailable or the DNS resolution failing. My suggestion is that you try using an external DNS host like Google's OpenDNS ( 8.8.8.8 ) to see if that helps w/ the connection.  Also be sure that the network connection is "always on" and not disconnecting when idle (some ISP's set that as a default and it takes a few seconds for a connection to be re-initiated again).
 
« Last Edit: July 21, 2011, 06:20:40 PM by TedDev »

scottf200b

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: Success rate for google PM or 3rd party products
« Reply #2 on: July 22, 2011, 09:42:03 AM »
Thank you very much for the prompt response.  I've been using the google DNSes for a very long time. 8.8.8.8/8.8.4.4  A ping of the 3rd party URL response immediately.  I have a fast broadband cable connection.  My http://www.speakeasy.net/speedtest/ shows 12.36 Mbps down and 4.12 up.

Attached is my Google PM that I have use for many month and it seems "solid" and graphs well.  (FYI, midnight to 3:30am usage is my Chevrolet Volt)

I'm a little concerned now with the "timeout" settings within both footprints and within the MTU?!?!?

Here are traceroutes for a couple google replacements.  I can not even activate ted.plotwatt.com and the other one took a few attempts.


Code: [Select]
C:\Documents and Settings\Scott>tracert data.myenersave.com -h 40 -w 50

Tracing route to data.myenersave.com [50.17.180.75]
over a maximum of 40 hops:

  1     1 ms    <1 ms    <1 ms  Administrator [24.15.xxx.xxx]
  2    34 ms    19 ms    20 ms  c-24-15-128-1.hsd1.il.comcast.net [24.15.xxx.xxx]
  3    22 ms    10 ms     8 ms  te-1-1-ur04.romeoville.il.chicago.comcast.net [68.86.118.217]
  4    18 ms    34 ms    11 ms  te-1-13-0-5-ar01.area4.il.chicago.comcast.net [68.87.230.121]
  5    13 ms    11 ms    11 ms  pos-1-11-0-0-cr01.chicago.il.ibone.comcast.net [68.86.95.9]
  6    13 ms    13 ms    17 ms  be-10-502-cr01.chicago.il.ibone.comcast.net [68.86.88.21]
  7    11 ms    11 ms    11 ms  xe-9-2-0.edge1.Chicago2.Level3.net [4.71.248.25]
  8    12 ms    12 ms    11 ms  vlan52.ebr2.Chicago2.Level3.net [4.69.138.190]
  9    40 ms    39 ms    38 ms  ae-6-6.ebr2.Washington12.Level3.net [4.69.148.145]
 10    39 ms    38 ms    40 ms  ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
 11    47 ms    43 ms    38 ms  ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
 12    39 ms    38 ms    38 ms  ae-1-80.edge1.Washington1.Level3.net [4.69.149.141]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15    38 ms    38 ms    38 ms  72.21.222.139
 16    46 ms    40 ms    41 ms  216.182.224.49
 17    39 ms    60 ms    41 ms  216.182.232.171
 18    38 ms    44 ms    60 ms  216.182.232.129
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.


Code: [Select]
C:\Documents and Settings\Scott>tracert ted.plotwatt.com

Tracing route to ted.plotwatt.com [69.164.199.181]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Administrator [24.15.xxx.xxx]
  2    27 ms    19 ms    15 ms  c-24-15-128-1.hsd1.il.comcast.net [24.15.xxx.xxx]
  3     7 ms     9 ms     9 ms  te-1-1-ur04.romeoville.il.chicago.comcast.net [68.86.118.217]
  4    12 ms    33 ms    16 ms  te-1-13-0-7-ar01.area4.il.chicago.comcast.net [68.86.187.169]
  5    13 ms    17 ms    11 ms  pos-1-15-0-0-cr01.chicago.il.ibone.comcast.net [68.86.93.181]
  6    12 ms    16 ms    11 ms  be-10-913-cr01.dallas.tx.ibone.comcast.net [68.86.88.45]
  7    39 ms    37 ms    39 ms  pos-1-12-0-0-cr01.denver.co.ibone.comcast.net [68.86.85.250]
  8    56 ms    56 ms    58 ms  pos-2-14-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.178]
  9    57 ms    63 ms    55 ms  pos-0-1-0-0-pe01.1950stemmons.tx.ibone.comcast.net [68.86.86.94]
 10    56 ms    57 ms    57 ms  theplanet-cr01.dallas.tx.ibone.comcast.net [75.149.228.2]
 11    57 ms    66 ms    57 ms  te2-2.dsr01.dllstx3.networklayer.com [70.87.255.26]
 12   226 ms   215 ms    67 ms  te3-2.dsr01.dllstx2.networklayer.com [70.87.253.130]
 13    54 ms    54 ms    55 ms  po1.car01.dllstx2.networklayer.com [70.87.254.74]
 14    66 ms    62 ms    57 ms  5a.7.1243.static.theplanet.com [67.18.7.90]
 15    55 ms    54 ms    55 ms  li114-181.members.linode.com [69.164.199.181]

Trace complete.


Thanks much in advance!!
« Last Edit: July 23, 2011, 09:19:13 AM by scottf200b »