WhatPulse 2.3b3

[smitmartijn]

Using the help of some beta users (thanks again!), I was able to get some more fixes in for 2.3. The two most important are the online application (uploading) and the possible crash when your system resumes from sleep. The rest are minor fixes, check the the complete list below!

Downloads:
- Windows: http://files.whatpulse.org/beta/whatpulse-win-2.3b3.exe
- OS X: http://files.whatpulse.org/beta/whatpulse-mac-2.3b3.dmg

Changes:

[Electrosa]

As I said on the other thread, these last versions are not counting all my network traffic. I have tested on two different computers. I've realized of the problem since 2.3b2, I don't know if 2.3b1 is affected too.

I have downloaded a 7 GB file with bittorrent, I have downloaded it two times: once with 2.3b2 and another one with 2.3b3 installed.



I have pulsed when the download finished and, as it can be seen, the first time only measured 1.58 GB of 7 GB, and the second 3.83/7 GB.

[Inquizitor]

Application info now shows up from all of my computers again! Thank you very much!

[smitmartijn]

(11-23-2013 03:18 PM)Electrosa Wrote:  As I said on the other thread, these last versions are not counting all my network traffic.

There's a limit to what pcap can handle..it's been optimised, but there will always be situations where the amount of traffic can't be handled. After long research and _everyone_ that has had problems in the past confirmed that the recent clients are counting properly, I'm not too bothered by the situations where if you download or upload with 150Mbit+ and it doesn't count everything. This thing is meant for desktops which usually don't have a connection higher than 50 to 100Mbit (in broadband areas).

[Electrosa]

(11-23-2013 04:46 PM)smitmartijn Wrote:  This thing is meant for desktops which usually don't have a connection higher than 50 to 100Mbit (in broadband areas).

I have 30 Mb/s at home and only 10 Mb/s at work. I will test it again with older versions, as 2.3b1 and 2.2.2b2.

[commentator]

Looks like there is a delay before the networkstats are available in Whatpulse (since current betas). Maybe that is your issue ?