> 12 processor Intel i7-8850 laptop which is running 100% so you must have
some good kit
I got those numbers on desktop i7-9700k. Laptops are still no match for
desktops (unfortunately).
> Does Java version have any bearing on performance?
Java version can certainly affect performance, but not in
Ok thanks.
I have managed to get the times down to 13 seconds write and 7.5 seconds
read, basically double your times, on my 12 processor Intel i7-8850 laptop
which is running 100% so you must have some good kit!
Does Java version have any bearing on performance?
--
Sent from: http://apache-ig
I've tried your code and got similar numbers (11s to write, 3s to read).
Profiler shows that serialization takes 90% of the streaming time (40% is
your WriteBinaryInternal method, the rest is Ignite internals)
Actual size of serialized object is 161 bytes, and
DataRegionMetris.TotalAllocatedSize is
It seems a combination of a better spec machine and a parallel for loop has
improved performance, although it still takes 8 seconds to run through all
the cache items.
Here is some basic test code...would appreciate any tips on how to improve
access in this type of usage pattern:
https://wtwdeepl
Can you please attach a working project to reproduce those numbers?
It is hard to say without the code: a class with 21 properties can vary in
size a lot.
There are many other things at play - JVM options, RAM size, benchmark
method, etc.
On Mon, Dec 2, 2019 at 2:08 PM camer314
wrote:
> I have
I have a 21 property C# class (mix of int and string) and am using
IBinarizable interface as suggested in the documentation.
My cache is configured such that each cache entry is a collection of these
objects, lets say each cache item is a List.
I have 10 million instance of this class. For simpli
