If Ignite can hold all the records in memory it won't be reading pages from
disk (the page replacement). Thus, it's expected that the 12GB performs
better than the 5GB case.
Btw, are you planning to reload the whole data set into Ignite on potential
cluster restarts? Each node loses a subset of th
Hi Denis,
We did a test, in the same environment (8G RAM, 10G swap partition) and
the same configuration (2G Heap, enable persistence, data volume is
about 6G), the only difference is that the maxSize size is different,
which is configured as 5G and 12G respectively. We found that the
perform
Ignite swapping is based on the swapping mechanism of the OS. So, you
shouldn’t see any difference if enable the OS one directly some way.
Generally, you should not use swapping of any form as a permanent
persistence layer due to the performance penalty. Once the swapping kicks
in, you should scal
Hi,
We retested and found that if we configured swapPath, as the amount of
data increased, the write speed was actually slower and slower. If the
amount of data is large, on average, it is much slower than the scenario
where native persistence is enabled and wal is disabled.
In this way, the
Agree with Ilya that the performance should be comparable if you disable
the WAL of the Ignite persistence.
Anyway, the swapping and Ignite persistence pursue different goals. The
swapping is one of the out-of-memory protection techniques - if you run out
of DRAM, then the OS will start swapping i
Hello!
I think the performance of swap space should be on par with persistence
with disabled WAL.
You can submit suggested updates to the documentation if you like.
Regards,
--
Ilya Kasnacheev
ср, 5 авг. 2020 г. в 06:00, 38797715 <38797...@qq.com>:
> Hi Ilya,
>
> If so, there are two ways to
Hi Ilya,
If so, there are two ways to implement ignite's swap space:
1. maxSize > physical memory, which will use the swap mechanism of the
OS, can be used *vm.swappiness* Adjust.
2. Configure the *swapPath* property, which is implemented by Ignite
itself, is independent of the OS and has no op
Hello!
>From the docs:
To avoid this situation with the swapping capabilities, you need to :
- Set maxSize = bigger_ than_RAM_size, in which case, the OS will take
care of the swapping.
- Enable swapping by setting the DataRegionConfiguration.swapPath
property.
I actually think th
Hi,
Documentation looks not very clean for me. Probably you should prepare your
operating system to use swap space. Can you try to prepare the swap file
first as following:
https://linuxize.com/post/how-to-add-swap-space-on-ubuntu-18-04/
And then choose this file.
BR,
Andrei
--
Sent from: h
Hi,
https://apacheignite.readme.io/docs/swap-space
According to the above document, if the physical memory is small, you
can solve this problem by opening the swap space,The specific method is
to configure maxSize to a larger value (i.e. larger than the physical
memory), and the swapPath prop
Hi,
Can you please clarify your expectations? You expected that JVM process will
be killed instead of gracefully stopping? What you are going to achieve?
BR,
Andrei
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi community,
When swapPath is configured in DataRegionConfiguration and maxSize is
greater than the physical memory (that is, swap space is enabled), if
the amount of data exceeds the physical memory, a node failure will
occur. The log is as follows:
[08:29:14,212][INFO][Thread-24][G] Invok
12 matches
Mail list logo
