Hi again,
So I made the memory mapped file changes to the Go version, and the results:
insert time 1000 records = 17890 ms, usec per op 1.7890143
close time 8477 ms
scan time 2887 ms, usec per op 0.2887559
scan time 50% 81 ms, usec per op 0.162584
random access time 3.508029 us per g
Hi all,
I had a opportunity to change the Java version to use memory mapped files,
using GraalVM:
insert time 1000 records = 15443ms, usec per op 1.5443
close time 4954ms
scan time 1934ms, usec per op 0.1934
scan time 50% 81ms, usec per op 0.162
random access time 6.264us per get
close with
Ask and ye shall receive…
So, first with running using the GraalVM JDK 11 Community Edition:
insert time 1000 records = 19305ms, usec per op 1.9305
close time 12313ms
scan time 10695ms, usec per op 1.0695
scan time 50% 461ms, usec per op 0.922
random access time 12.014us per get
close with me
I think it'd be a good idea if you can compile your Java port using GraalVM
and benchmark the generated executable.
On Monday, December 14, 2020 at 2:58:15 AM UTC+5:30 ren...@ix.netcom.com
wrote:
> I did not, and honestly it is probably not a great comparison.
>
> Java requires the JVM - which
I did not, and honestly it is probably not a great comparison.
Java requires the JVM - which is separate - so executables sizes are hard to
compare. The Java ‘executable code’ is tiny.
As for runtime memory usage, it is fairly trivial since the data is stored on
disk with an in-memory ’skip ind
Sorry. Repo should be accessible now. User error.
> On Dec 12, 2020, at 9:23 PM, Robert Engels wrote:
>
> It was a private repo - maybe there is a propagation delay. It should work.
>
>> On Dec 12, 2020, at 9:01 PM, max...@gmail.com wrote:
>>
>> i can not open the java version link https://
