public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "lsching17 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/50844] New: SimpleDateFormat too slow
Date: Mon, 24 Oct 2011 06:10:00 -0000	[thread overview]
Message-ID: <bug-50844-8172@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 50844
           Summary: SimpleDateFormat too slow
    Classification: Unclassified
           Product: gcc
           Version: 4.5.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcj
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: lsching17@gmail.com


The constructor of class "java.text.SimpleDateFormat" is too slow.

With the test script attached.

In a core 2 duo machine+linux kernel 2.6.38+1G ram, only around 70 objects can
be created per second

Compare to Sun jre 6 update 6, 100000+ objects can be created per second


             reply	other threads:[~2011-10-24  6:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24  6:10 lsching17 at gmail dot com [this message]
2011-10-24  6:13 ` [Bug libgcj/50844] " lsching17 at gmail dot com

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=bug-50844-8172@http.gcc.gnu.org/bugzilla/ \
    --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).