search

richb-hanover / ndt

Automatically exported from code.google.com/p/ndt
Other
1 stars 0 forks source link

Update to 3.6.5: possible java applet fault in S2C measurement/result display #66

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
User Christoph Ascendos <christoph.ascendos@chello.at> reported this error. His 
mail is below:
-----------------------------------------------------------------------
Hi,

I run the "yum update" today to update to 3.6.5 and tested the java applet via
internet explorer afterwards. The server is running on an internal gbit-lan.

According to previous tests with 3.6.4 the usuall BW is > 800 Mbit/s, for both
C2S and S2C. This is similar to the network load grafic in the windows task
manager (being between 80 and 90% for both tests).

The same test with 3.6.5 shows similar network load grafics in task manager
for both C2S and S2C, and the C2S result again shows values > 800 Mbit/s, but
S2C returns values around 20 Mbit/s for S2C test.

any thoughts?
---------- end mail ----------------

During the beta testing phase, user Ken Miller also reported seeing a negative 
number for the S2C throughput value. We were not able to reproduce it, but 
re-evaluation of the code shows that these 2 bugs are related.

Original issue reported on code.google.com by kumar.in...@gmail.com on 3 Aug 2012 at 7:55

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by kumar.in...@gmail.com on 3 Aug 2012 at 7:56

GoogleCodeExporter commented 9 years ago 
This should be fixed with NDT release v3.6.5.1. The fix was tested by 
Christoph, Andy and others who reported seeing expected values for all tests.

Original comment by kumar.in...@gmail.com on 8 Aug 2012 at 11:20

GoogleCodeExporter commented 9 years ago

Original comment by jslawin...@soldevelo.com on 25 Sep 2013 at 1:05

GoogleCodeExporter commented 9 years ago 
Already fixed in rev.778

Original comment by smale...@soldevelo.com on 17 Feb 2014 at 10:17