public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "mkrause at atronicsystems dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/19621] New: Network-performance issue in java.io.PrintStream
Date: Tue, 25 Jan 2005 11:41:00 -0000	[thread overview]
Message-ID: <20050125114112.19621.mkrause@atronicsystems.com> (raw)

When using a PrintStream in order to output 101 bytes via a socket, the output 
is split into to packets with 100 and 1 byte respectively. A native JDK sends 
101 bytes/packet.

The program reads

import java.io.PrintStream;
import java.net.Socket;
public class Test100ByteProblem {
	public static void main(String args[]){
		Socket s;
		try {
			int i = 0;
			s = new Socket("127.0.0.1", 3333);
			PrintStream ps = new PrintStream(s.getOutputStream());
			while(i++<20){
				ps.
print("qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
qqqqqqqqqqqqqqqqqqqqqqqqqqqq");
				ps.flush();
			}
			s.close();
		} catch (Exception e) {
			e.printStackTrace();
		}
	}
}


$gcj -v 
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/specs
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libgcj.spec
rename spec lib to liborig
Configured with: /var/tmp/portage/gcc-3.3.2/work/gcc-3.3.2/configure 
--prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.3 
--includedir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include 
--datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3 
--mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3/man 
--infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3/info --enable-shared 
--host=i686-pc-linux-gnu --target=i686-pc-linux-gnu --with-system-zlib 
--enable-languages=c,c++,f77,objc,java --enable-threads=posix --enable-long-long 
--disable-checking --enable-cstdio=stdio --enable-clocale=generic 
--enable-__cxa_atexit --enable-version-specific-runtime-libs 
--with-gxx-include-dir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include/g++-v3 
--with-local-prefix=/usr/local --enable-shared --enable-nls 
--without-included-gettext --x-includes=/usr/X11R6/include 
--x-libraries=/usr/X11R6/lib --enable-interpreter --enable-java-awt=xlib 
--with-x --disable-multilib
Thread model: posix
gcc version 3.3.2  (Gentoo Linux 3.3.2, propolice)

-- 
           Summary: Network-performance issue in java.io.PrintStream
           Product: gcc
           Version: 3.3.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mkrause at atronicsystems dot com
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19621


             reply	other threads:[~2005-01-25 11:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 11:41 mkrause at atronicsystems dot com [this message]
2005-01-29  0:27 ` [Bug libgcj/19621] " mckinlay at redhat dot com
2005-04-30 16:12 ` pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050125114112.19621.mkrause@atronicsystems.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).