|
Joe, In my case it did not seem to matter whether they were on the same machine or not. I got more consistent results on the same machine, but the best performance in this case came running the servlet off of the iSeries. This was about a year ago and the difference was around 4-5 times better with the tunneling approach. I do believe this difference was exaggerated due to a data queue wait problem is likely to have been fixed. It is always best to try these things out in your own environment; I was just curious to see if you had experienced this and wanted to find out if you knew of fixes or workaround. David Morris >>> joepluta@PlutaBrothers.com 08/30/01 05:13PM >>> David, I suspect that pure sockets is still the fastest way to go for remote clients. It's extra work, but hard to beat from an overhead standpoint. Personally, I like the data queue approach because most of my work uses servlets and the database tier and the presentation tier reside on the same machine, whihc may negate some of the benefits of the socket approach. I'd say that the best way to find out is simply to run some performance tests. Joe > -----Original Message----- > From: David Morris > > Next, I converted that same application to use http tunneling and > the performance > improvement was very noticeable. Since then, I know that data > queues have been > worked on. Do you know if the performance problems have been > fixed?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.