Search found 9 matches

by pempek
Tue Dec 22, 2015 5:41 am
Forum: Device Detection Issues
Topic: Java API performance issues
Replies: 15
Views: 11162

Re: Java API performance issues

Looks nicer, no calls to getSimpleName() are made. With the caching added, our servers perform now far better. Thank you!
by pempek
Mon Dec 21, 2015 7:24 am
Forum: Device Detection Issues
Topic: Java API performance issues
Replies: 15
Views: 11162

Re: Java API performance issues

Ok. Waiting for it to appear :)
by pempek
Wed Dec 16, 2015 5:23 am
Forum: Device Detection Issues
Topic: Java API performance issues
Replies: 15
Views: 11162

Re: Java API performance issues

I increased those values 10 times and now it works far better than at then beginning. Thanks for that tip and we're waiting for new version to come!:)
by pempek
Wed Dec 16, 2015 2:34 am
Forum: Device Detection Issues
Topic: Java API performance issues
Replies: 15
Views: 11162

Re: Java API performance issues

Do you mean:

Code: Select all

wurflEngine.setCacheProvider(new DoubleLRUMapCacheProvider(10_000, 25_000));
I'll try that and come back with results.
by pempek
Tue Dec 15, 2015 2:59 am
Forum: Device Detection Issues
Topic: Java API performance issues
Replies: 15
Views: 11162

Re: Java API performance issues

Sure.

Code: Select all

WURFLResource wurflResource = new XMLResource(file);
WURFLEngine wurflEngine = new GeneralWURFLEngine(wurflResource);
wurflEngine.setEngineTarget(EngineTarget.accuracy);
wurflEngine.getDeviceForRequest(""); // initialize
by pempek
Fri Dec 11, 2015 11:58 am
Forum: Device Detection Issues
Topic: Java API performance issues
Replies: 15
Views: 11162

Re: Java API performance issues

This is a snapshot of real code performance in our PROD servers. Our code is basically calling WURFLEngine.getDeviceForRequest(). The thing is that each server handles few thousand of requests per second. The side effect of that is high memory allocation rate (~350 MB/s) which is probably why we're ...
by pempek
Fri Dec 11, 2015 6:28 am
Forum: Device Detection Issues
Topic: Java API performance issues
Replies: 15
Views: 11162

Re: Java API performance issues

Upgraded to 1.6.4.0, does a little bit better, but mainly still the same issues. java.lang.Class.getSimpleName() consumes 1.8% CPU time out of 13.5% which WURFL consumes in overall. I'm preety sure those calls could be avoided/disabled. RISMatches still consumes ~70% of overall WURFL processing time...
by pempek
Thu Dec 10, 2015 2:07 am
Forum: Device Detection Issues
Topic: Java API performance issues
Replies: 15
Views: 11162

Re: Java API performance issues

The screenshot was taken at 1.5.2.1, but we're now migrated to 1.6.3.0 and it's still the same case.
by pempek
Wed Dec 09, 2015 2:48 am
Forum: Device Detection Issues
Topic: Java API performance issues
Replies: 15
Views: 11162

Java API performance issues

Hi, We're using Java API of WURFL and we're experiencing performance problems because of that. Analyzing WURFL call tree shows that there are several calls to java.lang.Class.getSimpleName(). In the attached example there are 4 calls (marked in red) which consume 10% of total WURFL processing time. ...