Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!nx02.iad01.newshosting.com!newshosting.com!news-out.readnews.com!news-xxxfer.readnews.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: Lew Newsgroups: comp.lang.java.programmer Subject: Re: Java Webstart network bandwidth Date: Mon, 19 Sep 2011 19:07:08 -0700 (PDT) Organization: http://groups.google.com Lines: 33 Message-ID: <18454261.934.1316484428293.JavaMail.geo-discussion-forums@prfb12> References: <827543cb-91c0-45ad-9bde-cf618253e858@e8g2000vbc.googlegroups.com> Reply-To: comp.lang.java.programmer@googlegroups.com NNTP-Posting-Host: 67.218.110.250 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1316484841 4788 127.0.0.1 (20 Sep 2011 02:14:01 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 20 Sep 2011 02:14:01 +0000 (UTC) In-Reply-To: <827543cb-91c0-45ad-9bde-cf618253e858@e8g2000vbc.googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=67.218.110.250; posting-account=CP-lKQoAAAAGtB5diOuGlDQk0jIwmH0T User-Agent: G2/1.0 X-Google-Web-Client: true Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:8169 bcr666 wrote: > I have a JWS application that accesses EJBs on a Borland Deploymnet > Platform. The application runs fine when run locally, but very slowly > when the client is remote (VPN). The remote connection is only using > about 256Kbps. Is there a way to tell it to use more? AIUI, Java WebStart is nothing but a delivery mechanism for an application = to reach the client machine. So another name for a "Java WebStart applicat= ion" is a "Java application". Look to your application for bad network hab= its. Many network-separated applications manage the "Great Divide" between nodes= very badly. Common mistakes include doing to little with each crossing, c= ausing communication overhead to dominate bandwidth; initiating a send from= both ends to each other, instead of having one end be requester-only (the = client) and the other responder-only (the server); and using file I/O as in= termediate steps. There are network factors beyond the program's control, of course. The ser= ver connection just might be over a very thin pipe. There's not enough information in your post for us to diagnose what your bo= ttleneck is. Run some diagnostics, such as a bandwidth test (or at least a= ping) between the nodes involved. If your bandwidth is only 256 Kbps betw= een the nodes, nothing is going to go much faster over that link. (You can= play games with compression to increase the perceived bandwidth, but that = comes at a cost of effort and complexity.) Give us more data to work with, and look into what your application is doin= g with its bandwidth. --=20 Lew