Hello! It is possible that your primary key would not fit into index and walking index tree will put unnecessary strain on persistent page memory.
On 2.7 there will be a warning about that in log. Please try to tune IGNITE_MAX_INDEX_PAYLOAD_SIZE system property since it's the only available means of changing that value. Try to put something line 32 or 64 there, see if it helps. Regards, -- Ilya Kasnacheev вт, 26 февр. 2019 г. в 20:24, Antonio Conforti <[email protected]>: > Hello, > > > I recap the scenario of benchmark: > > 1) Constant submission of 4000 entries per second where every entry is an > add (the key contains a field updatetime and changes for every entry). > 2) The benchmark starts with no data in cache and the entries are submitted > from an Ignite client node in the cluster using the StreamVisitor.addData() > method (located on HOST1). > 3) The cluster is composed of a total of 8 ignite server nodes: server > nodes > with consistence ID 1,3,5,7 on HOST1 and server nodes with consistence ID > 2,4,6,8 on HOST2; > > > Below the general configuration: > > Cache configuration: > > 1. TRANSACTIONAL > 2. partitioned > 3. with backup 1 (and affinity with exclude neighbours enabled) > 4. write synchronization mode FULL_ASYNC > 5. indexed on key and value (and enabled to SQL inquiry) > > > We have also configured: > 1. failureDetectionTimeout to 120000msec > 2. Data region (only 1): > a. Persistence enabled > b. max size 8 GB > c. checkpointPageBufferSize 2 GB > 3. WAL mode LOG_ONLY > 4. disabled WAL archiving (WAL path and the WAL archive path to > the same > value) > 5. Pages Writes Throttling enabled > > > I run also a second scenario with frequency set to 600000 (10minutes) as > suggested and with direct IO enabled and WAL mode set to NONE. > > > For problem of space you can find logs and configuration file of only > server > node 1 attached for both scenarios as described below: > > 1) folder 20190222: log and config for scenario 1) > 2) folder 20190225: log and config for scenario 2) > 3) IGN_DF_CMF_QUOTE_PK.java: key entity inserted in cache > 4) IGN_DF_CMF_QUOTE.java: entity data inserted in cache > > case-Ignite.zip > <http://apache-ignite-users.70518.x6.nabble.com/file/t2315/case-Ignite.zip> > > > If you need another benchmark with specific configuration, just let me > know. > > Thanks. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
