views:

13

answers:

0

Hi,

I'm debugging my WebApp using JPDA, running on tomcat5.5 on Debain 5 (Alestic) in EC2 us-east region. And this is painfully slow.

I'm connection from Israel, simple ping requests to the server:

Ping:

C:\Users\User>ping -t 174.129.xxx.xxx

Pinging 174.129.xxx.xxx with 32 bytes of data:
Reply from 174.129.xxx.xxx: bytes=32 time=171ms TTL=39
Reply from 174.129.xxx.xxx: bytes=32 time=169ms TTL=39
Reply from 174.129.xxx.xxx: bytes=32 time=171ms TTL=39
Reply from 174.129.xxx.xxx: bytes=32 time=173ms TTL=39
Reply from 174.129.xxx.xxx: bytes=32 time=166ms TTL=39
Reply from 174.129.xxx.xxx: bytes=32 time=170ms TTL=39
Reply from 174.129.xxx.xxx: bytes=32 time=170ms TTL=39
Reply from 174.129.xxx.xxx: bytes=32 time=168ms TTL=39
Reply from 174.129.xxx.xxx: bytes=32 time=175ms TTL=39

Trace route:

C:\Users\User>tracert 174.129.xxx.xxx

Tracing route to ec2-174-129-xxx-xxx.compute-1.amazonaws.com [174.129.xxx.xxx]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  80.179.xxx.xxx.forward.012.net.il [80.179.xxx.xxx]
  2    19 ms    23 ms    20 ms  BRAS-MRK02-015-LO.012.net.il [212.199.139.49]
  3    25 ms    19 ms    19 ms  BRAS-MRK-02-CORE-Lo.bb.012.net.il [212.199.17.7]
  4    35 ms    19 ms    19 ms  CORE-1.MRK-vl744.bb.012.net.il [212.199.139.17]
  5    18 ms    19 ms    19 ms  BRDR.MR-01-gig0-1-0.bb.012.net.il [212.199.5.33]
  6    75 ms    95 ms    76 ms  EDGE.FRA-02-RE1-so-2-1-0-3-0.bb.012.net.il [80.179.166.29]
  7    94 ms    91 ms    89 ms  77.67.61.145
  8   168 ms   170 ms   169 ms  xe-0-0-0.was12.ip4.tinet.net [89.149.185.1]
  9     *        *        *     Request timed out.
 10   171 ms   172 ms   169 ms  72.21.197.38
 11   171 ms   191 ms   170 ms  72.21.222.155
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16   171 ms   170 ms   172 ms  ec2-174-129-xxx-xxx.compute-1.amazonaws.com [174.129.xxx.xxx]

Trace complete.

I've found some very old (2006) references to bugs of this kind:

But I don't think this is the issue now.

My software versions:

Server:

Debian 5
java version "1.5.0_17"
tomcat5.5

Client:

Windows 7 64bit
java version "1.6"
Eclipse 3.5

Question is:

What (if at all) can be done to speed up this thing?

  • Can I tunnel the traffic through some compression proxy?
  • Maybe I can connect on a port that is considered "Streaming port"? (That should give my pockets priority at the various IPS's along the way). If so then which one?
  • More ideas?

Thanks for reading guys, Maxim.