ehCache even doesn's serialize data, reading it directly from Java
heap once you allocate your objects. It's designed for local mode use cases
like HashMap.
Compare ehCache to Ignite in the distributed mode. Ignite was designed and
optimized to work at scale.
--
Denis
On Mon, Oct 1, 2018 at
It means ehCache is better than ignite performance atleast in LOCAL mode :)
I fully expect ehCache, Guava Cache, etc to be faster than Ignite since Ignite
has more to do to communicate with the grid. But the scale of the difference is
the concern, Thus far my experiments do not show it's
It means ehCache is better than ignite performance atleast in LOCAL mode :)
On 22-Sep-2018 3:33 AM, "Daryl Stultz" wrote:
> I've discovered that "partitioned" is the default Cache Mode. I set it to
> "local". Things run faster now. Still not as fast as expected.
>
> 2018-09-21 20:54:41.733
I've discovered that "partitioned" is the default Cache Mode. I set it to
"local". Things run faster now. Still not as fast as expected.
2018-09-21 20:54:41.733 DEBUG - c.o.i.IgniteSpec : load 428765 rows into local
map in 976 ms
2018-09-21 20:54:43.562 DEBUG - c.o.i.IgniteSpec : putAll map to
is my understanding correct, that you first select 400k records from DB, DB
is remote and this takes 700ms, then you select all these 400k records from
Ignite and now it takes 500ms, but in this case ignite is a local embedded
node?
All of this runs on my laptop, no network involved. MacBook
Hi Daryl,
Could you please share with us your benchmark?
is my understanding correct, that you first select 400k records from DB, DB
is remote and this takes 700ms, then you select all these 400k records from
Ignite and now it takes 500ms, but in this case ignite is a local embedded
node?
Hello,
I am trying out Ignite for the first time. I have some interesting performance
metrics that are unexpected. I'm looking to see if my understanding of what
Ignite is meant to do is correct.
I have 400K records from a database that I am loading into a cache with the
primary key mapped
