Mailing-List: contact dev-help@devicemap.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@devicemap.apache.org
Received-SPF: pass (nike.apache.org: domain of werner.keil@gmail.com
 designates 209.85.214.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <281202337.7922423.1418229785999.JavaMail.yahoo@jws106143.mail.bf1.yahoo.com>
References: 
 <CAP7pH7senn=fhBhdpzUar65YvMbmqp4QzTZKboKSvb2zjCQBYg@mail.gmail.com>
	<281202337.7922423.1418229785999.JavaMail.yahoo@jws106143.mail.bf1.yahoo.com>
Date: Wed, 10 Dec 2014 18:13:57 +0100
Message-ID: 
 <CAAGawe1oEEyiRQ26QoD3r0kiL=pGzEefp9igb2AA-7QQiG-gpQ@mail.gmail.com>
Subject: Re: 2x Performance Increase in classify()
From: Werner Keil <werner.keil@gmail.com>
To: dev@devicemap.apache.org, Reza Naghibi <reza.naghibi@yahoo.com>
Content-Type: multipart/alternative; boundary=089e0149d084f910a10509dfc865

--089e0149d084f910a10509dfc865
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Volkan/Reza,

Let's keep in mind, the W3C DDR implementation has specialized recognition
classes like OrderedTokenDeviceBuilder or TwoStepDeviceBuilder and
subclasses that analyze the UserAgent more thoroughly, and currently
provide better recognition of say an update to Android 4 or 5.

Werner


On Wed, Dec 10, 2014 at 5:43 PM, Reza Naghibi <
reza.naghibi@yahoo.com.invalid> wrote:

> Volkan,
>
> Thanks for the performance patch. I reviewed it and it looks pretty good.
> Pre patch, we were running each ngram set thru some raw string processing
> normalizations. You patch does a good job moving that to the beginning an=
d
> optimizing the regex. Good job :)
>
> As for pattern matching, if you look at the normalization method, we only
> look at alpha-numerics. This was done for simplicity sake. The downside
> here is that we weaken any pattern which contains non alpha numerics. The=
re
> are several ways to address and fix this, but since DeviceMap has control
> over its own data, I prefer fixing the patterns and keeping the matching
> engine simple. The thing to remember is that our data came from OpenDDR
> which had a more complex classification algorithm and heuristics, so we
> kind of have a bit of legacy baggage to sort thru as this project evolves=
.
>
> Regarding our next release, I already have the Java client 1.1.0 ready to
> go. I would like to get your patch in on the next release, 1.1.1.
>
> Reza
>
>
>       From: Volkan YAZICI <volkan.yazici@gmail.com>
>  To: "devicemap-dev@incubator.apache.org" <
> devicemap-dev@incubator.apache.org>
>  Sent: Wednesday, December 10, 2014 9:32 AM
>  Subject: 2x Performance Increase in classify()
>
> Good news everyone!
>
> Here is the patch that introduces JMH-based benchmarks for Java client:
> DMAP-106 <https://issues.apache.org/jira/browse/DMAP-106>
>
> And here is the patch that introduces >2x performance gain: DMAP-107
> <https://issues.apache.org/jira/browse/DMAP-107>
>
> *Sample output:*
>
> $ export userAgentFile=3D/path/to/user-agents.txt
> $ wc -l $userAgentFile
> 195325
> $ java \
>     -jar
> devicemap/java/classifier-benchmark/target/devicemap-client-benchmark.jar
> \
>     -jvmArgsAppend "-server -XX:+TieredCompilation -XX:+AggressiveOpts
> -Xms1024m -Xmx4096m -DuserAgentFile=3D$userAgentFile" \
>     -wi 5 -i 5 -bm avgt -tu ms -f 3 \
>     ".*DeviceMapClientBenchmark.*"
>
> # Using the most recent trunk.
> Result: 12079.408 =C2=B1(99.9%) 1240.628 ms/op [Average]
>   Statistics: (min, avg, max) =3D (11232.424, 12079.408, 16011.000),
> stdev =3D 1160.484
>   Confidence interval (99.9%): [10838.781, 13320.036]
>
> # Using the enhanced classify().
> Result: 5505.355 =C2=B1(99.9%) 441.748 ms/op [Average]
>   Statistics: (min, avg, max) =3D (5060.269, 5505.355, 6508.699), stdev =
=3D
> 413.211
>   Confidence interval (99.9%): [5063.607, 5947.103]
>
>
> Cheers!
>
>
>

--089e0149d084f910a10509dfc865--