From issues-return-56816-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Feb 5 15:51:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id CD1EB180647 for ; Mon, 5 Feb 2018 15:51:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BD205160C5A; Mon, 5 Feb 2018 14:51:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8CB79160C46 for ; Mon, 5 Feb 2018 15:51:03 +0100 (CET) Received: (qmail 99091 invoked by uid 500); 5 Feb 2018 14:51:02 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 99081 invoked by uid 99); 5 Feb 2018 14:51:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Feb 2018 14:51:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 5EEFCC1588 for ; Mon, 5 Feb 2018 14:51:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id nYp6ip-jsGKg for ; Mon, 5 Feb 2018 14:51: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 1D18C5F5FB for ; Mon, 5 Feb 2018 14:51: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 6077DE008D for ; Mon, 5 Feb 2018 14:51: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 21F3321E82 for ; Mon, 5 Feb 2018 14:51:00 +0000 (UTC) Date: Mon, 5 Feb 2018 14:51:00 +0000 (UTC) From: "Dmitriy Pavlov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-7627) Introduce a new page rotation policy to avoid replacement of primary Index pages 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/IGNITE-7627?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7627: ----------------------------------- Description:=20 It would be great if we can have a new type of page replacement policy that= does not affect index pages when persistence=C2=A0is on. So, the index pag= es always will be in-mem and that will improve an overall system performanc= e=C2=A0for random reads with persistence is on. For instance, MongoDB works that way. It always keeps all indexes in-mem. was: It would be great if we can have a new type of eviction policy that does no= t affect index pages when persistence=C2=A0is on. So, the index pages alway= s will be in-mem and that will improve an overall system performance=C2=A0f= or random reads with persistence is on. For instance, MongoDB works that way. It always keeps all indexes in-mem. > Introduce a new page rotation policy to avoid replacement of primary Inde= x pages > -------------------------------------------------------------------------= ------- > > Key: IGNITE-7627 > URL: https://issues.apache.org/jira/browse/IGNITE-7627 > Project: Ignite > Issue Type: Improvement > Components: persistence > Reporter: Alexey Popov > Priority: Major > > It would be great if we can have a new type of page replacement policy th= at does not affect index pages when persistence=C2=A0is on. So, the index p= ages always will be in-mem and that will improve an overall system performa= nce=C2=A0for random reads with persistence is on. > For instance, MongoDB works that way. It always keeps all indexes in-mem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)