flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Jerman <st...@kloudspot.com>
Subject Re: In-Memory data grid
Date Mon, 03 Apr 2017 17:23:59 GMT
I had a DB look up to do and  used com.google.common.cache.Cache with a 10 sec timeout:

private static Cache<String, String> locationCache = CacheBuilder.newBuilder().maximumSize(1000).expireAfterAccess(10,

Seemed to help a lot with throughput….


On Apr 3, 2017, at 10:55 AM, nragon <nuno.goncalves@wedotechnologies.com<mailto:nuno.goncalves@wedotechnologies.com>>

Just to add a scenario.

My current arquitecture is the following:
I've deployed 4 ignite node in yarn and 5 task managers with 2G and 2 slots
As cache on ignite I have on record in key/value (string, object[])
My thoughput without ignite is 30k/sec when I add the lookup i get 3k/sec

My question is, has anyone used ignite as fast lookup or any other in memery
data grid? If so, did you have any major performance impact?


View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/In-Memory-data-grid-tp12494p12510.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com<http://Nabble.com>.

View raw message