October 03, 2003
JPDA debugging is slow over a VPN
Just working from home today, VPNed in to the office using my cable modem and man, debugging a Java JVM in the office from Eclipse at home is painful. There isn't a lot of traffic but the latency of the VPN connection seems to drag it down a lot.
Granted not a lot of developers probably do this but when ever I get time, I think I'll look at JPDA and see why it's so latency senstive.
October 3, 2003 | Permalink
I've hacked JDWP to death. I don't think it has an implicitly high latency (you can make several requests before receiving the reply to the first), I imagine it's just that most debugger developers need the results of queries before deciding what to ask for next.
There isn't a whole lot of caching going on underneath, so for *every* breakpoint, you have to re-ask for details about every local variable (for instance).
Posted by: Paul Mclachlan | Oct 3, 2003 1:31:46 PM
I also thought this - until I discovered that the 'puter could not resolve the jvm's ip address to a hostname...after adding the machine to my hosts file - everything work as the computers where side-by-side ......
just a possible solution...
Posted by: Max | Oct 3, 2003 4:43:50 PM
Got a host name in my local hosts file so that ain't it.
Posted by: Billy | Oct 3, 2003 11:03:44 PM