11-07-2020, 08:02 AM
(This post was last modified: 11-07-2020, 08:16 AM by troublebass.)
(11-05-2020, 10:12 PM)drummer1154 Wrote: Can you please enter on a win10 cmd line (for Mac/linux I do not know the command)>>>
ping -l 1000 -n 50 <peer_IP-or-DDNS_addr>
for each peer and report the average RTT. Buffer size 1000 bytes is important, the default 32 bytes do not result in reproduceable results.
Are all peers on the same ISP?
Our 3-piece band located in Munich encountered unmanageable delay times, most likely because we are on 3 different ISPs (Telekom, VF/KabelDeutschland, SWM). I believe all packets need to be routed via Frankfurt.
Cheers
-hg
We will do that in our next test session. However, what will we do with the result? Which pameter can we change to improve the result? I understand that you are stuck as well, right
(11-06-2020, 02:18 AM)StuartR Wrote: While I cannot speak for the JK team, I'll hazard a guess that their new network acceleration network connectivity might be the culprit here. Here's what they told us at the end of September in their last email update:
"Latency Reduction & Connectivity Improvements
In our last email, we shared some data on the latency reduction and connectivity success rates we can see from our new networking technologies. We have been continuing to complete the implementation of this set of technologies. It’s pretty complex stuff, so it’s taking time. There is also a limit to how much we can test it ourselves without pu$ng it out onto the platform, so the transition period as we release and harden this technology is going to be a little bumpy - but worth it!"
>>>
That sounds similar to what Dimitri wrote. So, let's wait for a new version of JK?
Email from JamKazam: Does every registered JK user get such Emails automatically or did I miss a tickbox somewhere in JK or in the forum?