Return-Path: Delivered-To: apmail-harmony-commits-archive@www.apache.org Received: (qmail 22824 invoked from network); 12 Feb 2008 13:25:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Feb 2008 13:25:41 -0000 Received: (qmail 1266 invoked by uid 500); 12 Feb 2008 13:25:35 -0000 Delivered-To: apmail-harmony-commits-archive@harmony.apache.org Received: (qmail 1250 invoked by uid 500); 12 Feb 2008 13:25:34 -0000 Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list commits@harmony.apache.org Received: (qmail 1241 invoked by uid 99); 12 Feb 2008 13:25:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2008 05:25:34 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2008 13:24:47 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 46BBE714079 for ; Tue, 12 Feb 2008 05:25:08 -0800 (PST) Message-ID: <19643350.1202822708287.JavaMail.jira@brutus> Date: Tue, 12 Feb 2008 05:25:08 -0800 (PST) From: "Aleksey Shipilev (JIRA)" To: commits@harmony.apache.org Subject: [jira] Commented: (HARMONY-5396) [drlvm][em] excess ValueProfiler locking causes degradation on JITted code with profiling In-Reply-To: <33481235.1200494074776.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HARMONY-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568105#action_12568105 ] Aleksey Shipilev commented on HARMONY-5396: ------------------------------------------- > I think, this is enough to prove that we can move on with the current precision Egor, the thing is, lack of accurate profiling can cause _intermittent_ performance degradations, which we wouldn't quickly notice. That's the price we would pay for speed of startup, and then we should resort to inaccurate profiling only in case of startup-important workloads. I think precise (e.g. locked) profiling should reside as default. > [drlvm][em] excess ValueProfiler locking causes degradation on JITted code with profiling > ----------------------------------------------------------------------------------------- > > Key: HARMONY-5396 > URL: https://issues.apache.org/jira/browse/HARMONY-5396 > Project: Harmony > Issue Type: Improvement > Components: DRLVM > Reporter: Aleksey Shipilev > Assignee: Egor Pasko > Attachments: 0001-ValueProfileCollector-refactoring-to-separate-FirstN-and-Divided-methods.txt, 0002-value-profiling-options-locked-flagged_all-flagged_insert-unsafe.txt, 0002-ValueProfileCollector-implementing-locking-strategies.txt, 0003-value-profiling-options-locked-flagged_all-flagged_insert-unsafe.txt, HARMONY-5396-syncTie.patch > > > During investigation of serious slowdown in some microbenchmark, excess locking in ValueProfiler was identified. > Please see Harmony-dev thread for the details: http://markmail.org/message/tatsfbyb7eb3q3rr -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.