From oak-issues-return-57528-apmail-jackrabbit-oak-issues-archive=jackrabbit.apache.org@jackrabbit.apache.org Wed Dec 6 10:13:03 2017 Return-Path: X-Original-To: apmail-jackrabbit-oak-issues-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-oak-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8DC1E10773 for ; Wed, 6 Dec 2017 10:13:03 +0000 (UTC) Received: (qmail 5500 invoked by uid 500); 6 Dec 2017 10:13:03 -0000 Delivered-To: apmail-jackrabbit-oak-issues-archive@jackrabbit.apache.org Received: (qmail 5463 invoked by uid 500); 6 Dec 2017 10:13:03 -0000 Mailing-List: contact oak-issues-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-issues@jackrabbit.apache.org Received: (qmail 5451 invoked by uid 99); 6 Dec 2017 10:13:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Dec 2017 10:13:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 9B7AA180701 for ; Wed, 6 Dec 2017 10:13:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id jKpz9oZeGYe7 for ; Wed, 6 Dec 2017 10:13:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3C7CC5F216 for ; Wed, 6 Dec 2017 10:13:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 84962E0662 for ; Wed, 6 Dec 2017 10:13:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4A427255C8 for ; Wed, 6 Dec 2017 10:13:00 +0000 (UTC) Date: Wed, 6 Dec 2017 10:13:00 +0000 (UTC) From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= To: oak-issues@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OAK-6984) High read IO in compaction retry cycles MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OAK-6984?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Michael D=C3=BCrig updated OAK-6984: ------------------------------- Issue Type: Bug (was: Improvement) > High read IO in compaction retry cycles > --------------------------------------- > > Key: OAK-6984 > URL: https://issues.apache.org/jira/browse/OAK-6984 > Project: Jackrabbit Oak > Issue Type: Bug > Components: segment-tar > Reporter: Michael D=C3=BCrig > Assignee: Michael D=C3=BCrig > Labels: performance > Fix For: 1.8, 1.7.13 > > Attachments: compactioncycles.m, cpu.png, cycle-times.png, cycles= .png, extract.sc, gcmetrics-15.png, gcmetrics-20.png, gcmetrics.m, readwrit= e.m, readwrite.png > > > We have seen unusual high read IO in compaction retry cycles in our longe= vity tests at Adobe. > !cpu.png|width=3D1000! > Above picture shows the CPU utilisation during an online compaction run, = which starts at 03:00. At about 03:22 CPU user time drops and CPU waiting f= or IO time increases. This point in time coincides with the start of the fi= rst retry cycle of compaction.=20 -- This message was sent by Atlassian JIRA (v6.4.14#64029)