From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 42089 invoked by alias); 24 Mar 2016 21:02:42 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 42073 invoked by uid 89); 24 Mar 2016 21:02:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=UD:jpg, closer, super, huge X-HELO: mail-qk0-f182.google.com Received: from mail-qk0-f182.google.com (HELO mail-qk0-f182.google.com) (209.85.220.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 24 Mar 2016 21:02:30 +0000 Received: by mail-qk0-f182.google.com with SMTP id s5so25021432qkd.0 for ; Thu, 24 Mar 2016 14:02:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JILZxV7XeBxGKSubHfhImIPyfnLgolWtRA2um5LLoLw=; b=AEXXmfBQxWu3spwqk8D6VnVdoJoLQaa9tayAl80XGsPA/uitT1SJanM6PE1nx382+b scIBS3qB5CVjoGR5hJlSL8n6StFFEP8RcxE9DdQ4yuimhjWJI0InKCHZix2V31uNjsYU 9E10X1bnM1kgJ0TASN5RuMNgiedVshn1Uduu14zMnqSGHefg1fZE8NI3/q/mK1eV7LlN 9mVEchpsMvOPr9Hr2X2/nqRjJsH9oopC60jUOghUfwnfvqF6CTzmAo6tcECNlYBtWRe7 gsU/Pp0B6/J0sXjcCMhOYJuHnucgrr+Q5nl5sVNI4HIm7XGqNJEwSPKxejF//kSlGWB/ 6hSA== X-Gm-Message-State: AD7BkJLOR2EAg3D1Li3d/LsAFSswMPB8m34yZzELzLa/pURsPJfXzpdcEy1HBM2CnJmLOtOdsiBeIdcsWruTeA== X-Received: by 10.55.203.200 with SMTP id u69mr13293427qkl.51.1458853348410; Thu, 24 Mar 2016 14:02:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.189.130 with HTTP; Thu, 24 Mar 2016 14:02:08 -0700 (PDT) In-Reply-To: References: <56F168D7.9050405@redhat.com> <56F16F8F.9050404@redhat.com> <56F1759F.3070100@redhat.com> <56F17A23.90909@redhat.com> <56F2DF69.9030908@redhat.com> <56F2F31F.4000104@redhat.com> <56F34041.2000301@redhat.com> From: Yichao Yu Date: Thu, 24 Mar 2016 21:02:00 -0000 Message-ID: Subject: Re: JIT debugging (Attach and speed) To: Pedro Alves Cc: gdb@sourceware.org, Paul Pluzhnikov Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2016-03/txt/msg00047.txt.bz2 > There's indeed a huge improvement. The test I was using with ~2000 JIT > objects goes drops from ~400s to 7.5s (~3s without gdb). However a > rough scaling test suggests that the scaling is still ~O(n^2) 20k JIT > objects takes ~500s (~130s without gdb). It seems that the master was > actually super quadratic (if this is a word) when dealing with > multiple JIT objects. The new profile is [1] and it is indeed much closer to the one in 2011. [1] http://i.imgur.com/K3GKYeq.jpg > >> Having a pending breakpoint that is never resolved slows things down >> significantly again though... The perf profile shows that breakpoint_re_set >> ends up calling parse_linespec which wants the selected block, which wants >> the selected frame, and then we're back at the same... Maybe we >> could reconsider how pending breakpoints are re-parsed, and which >> context they're parsed in. Not sure. >> >> Still, very promising. >> > > Indeed. It's already so much better.