Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 82217183DF for ; Thu, 13 Aug 2015 20:42:47 +0000 (UTC) Received: (qmail 13840 invoked by uid 500); 13 Aug 2015 20:42:47 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 13791 invoked by uid 500); 13 Aug 2015 20:42:47 -0000 Mailing-List: contact user-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.incubator.apache.org Delivered-To: mailing list user@ignite.incubator.apache.org Received: (qmail 13782 invoked by uid 99); 13 Aug 2015 20:42:47 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Aug 2015 20:42:47 +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 EA06CDDA02 for ; Thu, 13 Aug 2015 20:42:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.975 X-Spam-Level: *** X-Spam-Status: No, score=3.975 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.006, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 2VjVKPciMBma for ; Thu, 13 Aug 2015 20:42:39 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with SMTP id 9F59B42B21 for ; Thu, 13 Aug 2015 20:42:38 +0000 (UTC) Received: (qmail 13609 invoked by uid 99); 13 Aug 2015 20:42:38 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Aug 2015 20:42:38 +0000 Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com [209.85.214.181]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id EB9961A0325 for ; Thu, 13 Aug 2015 20:42:37 +0000 (UTC) Received: by obbop1 with SMTP id op1so46854953obb.2 for ; Thu, 13 Aug 2015 13:42:37 -0700 (PDT) X-Gm-Message-State: ALoCoQngaWUDkxMN/9uzNQraGp4XqQMOOaXl8PNdz++UXoh52DjNLmDbN3Il9gZeAm9LknlyjGdm X-Received: by 10.60.15.133 with SMTP id x5mr36019561oec.80.1439498557045; Thu, 13 Aug 2015 13:42:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.190.70 with HTTP; Thu, 13 Aug 2015 13:41:57 -0700 (PDT) In-Reply-To: References: <1439410869266-936.post@n6.nabble.com> <1439416662658-938.post@n6.nabble.com> <1439475853150-945.post@n6.nabble.com> From: Dmitriy Setrakyan Date: Thu, 13 Aug 2015 13:41:57 -0700 Message-ID: Subject: Re: Multiple indexes. To: user Content-Type: multipart/alternative; boundary=089e014945c025de15051d37608a --089e014945c025de15051d37608a Content-Type: text/plain; charset=UTF-8 @javadevmtl - Do you have a test we can use to reproduce it? You can either provide a github repo link or paste your code into a Gist or Pastebin. D. On Thu, Aug 13, 2015 at 1:37 PM, Sergi Vladykin wrote: > Yes, this can be related to serialization. I think we should test this > ourselves to make sure. > Igniters, can someone add such a benchmark to our performance suite and > check what happens? > > Sergi > > 2015-08-13 17:24 GMT+03:00 javadevmtl : > >> I think I know what it is... >> >> It's not GC everything is off-heap and I start VM with XMX4g which is more >> then enough heap to handle the incoming HTTP requests parse the json, >> convert to object and serialize in the off-heap cache. >> >> Basically, the model has 12 fields. 2 of those fields are "home" address >> fields e.g: 1234 Street, Apt: 9, New York... And they can be up to 240 >> characters, so 480 characters total. >> >> I removed those 2 fields for now and I can index 10 fields (most of which >> are still strings of 60 chars) at 11K requests per second with no >> slowdown. >> >> So the 2 fields either 2 long for an index or affecting serialization to >> the >> cache??? >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/Multiple-indexes-tp936p945.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > > --089e014945c025de15051d37608a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
@javadevmtl - Do you have a test we can use to reproduce i= t? You can either provide a github repo link or paste your code into a Gist= or Pastebin.

D.

On Thu, Aug 13, 2015 at 1:37 PM, Sergi Vladykin <sergi.vladykin@gmail.com> wrote:
Yes, this can be related to serialization. = I think we should test this ourselves to make sure.
Igniters, can someo= ne add such a benchmark to our performance suite and check what happens?

Sergi

2015-08-13 17:24 GMT+03:00 javadevmtl <java.dev.= mtl@gmail.com>:
I think I k= now what it is...

It's not GC everything is off-heap and I start VM with XMX4g which is m= ore
then enough heap to handle the incoming HTTP requests parse the json,
convert to object and serialize in the off-heap cache.

Basically, the model has 12 fields. 2 of those fields are "home" = address
fields e.g: 1234 Street, Apt: 9, New York... And they can be up to 240
characters, so 480 characters total.

I removed those 2 fields for now and I can index 10 fields (most of which are still strings of 60 chars) at 11K requests per second with no slowdown.=

So the 2 fields either 2 long for an index or affecting serialization to th= e
cache???







--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Multiple-indexes-tp9= 36p945.html
Sent from the Apache Ignite Users mailing list archive at Nabble.= com.


--089e014945c025de15051d37608a--