We've already tried that but we are receiving these errors. We are using
index in a correct way only
We are using Ignite persistence.
```
[15:32:19,481][WARNING][long-qry-#110][LongRunningQueryManager] Query
execution is too long [duration=3898ms, type=MAP, distributedJoin=false,
enforceJoinOrder=false, lazy=false, schema=PUBLIC, sql='SELECT
"__Z0"."ID" "__C0_0",
"__Z0"."URL" "__C0_1",
"__Z0"."SCORE" "__C0_2",
"__Z0"."APPNAME_ID" "__C0_3"
FROM "PUBLIC"."URLS" "__Z0"
WHERE "__Z0"."APPNAME_ID" = ?1
ORDER BY 3 FETCH FIRST ?2 ROWS ONLY', plan=SELECT
__Z0.ID AS __C0_0,
__Z0.URL AS __C0_1,
__Z0.SCORE AS __C0_2,
__Z0.APPNAME_ID AS __C0_3
FROM PUBLIC.URLS __Z0
/* PUBLIC.IDX_2_URLS */
/* scanCount: 1342938 */
WHERE __Z0.APPNAME_ID = ?1
ORDER BY 3
FETCH FIRST ?2 ROWS ONLY
/* index sorted */, node=TcpDiscoveryNode
[id=1acf85ab-112a-4bbf-95f3-b6d3eb8c38b8,
consistentId=1acf85ab-112a-4bbf-95f3-b6d3eb8c38b8, addrs=ArrayList
[127.0.0.1, 192.168.177.58], sockAddrs=HashSet [/127.0.0.1:0,
/192.168.177.58:0], discPort=0, order=4, intOrder=4,
lastExchangeTime=1589276400188, loc=false,
ver=8.7.10#20191227-sha1:c481441d, isClient=true], reqId=482, segment=0]
```
The thing is we are running this in an 8 GB machine. According to the
documents about tuning, we were told that 70% of the RAM should be given to
heap and non heap so we gave 2GB heap + 2GB offheap + 1GB directbuffmemory..
Till 60Lakh records, it didn't throw any warnings, but after that we are
receiving many warnings.
Is it got to do something with Off-heap size or BTree data size that is
stored in RAM? Should we increase RAM? We don't want to increase RAM. Is it
possible without increasing RAM? Or is there a way we can calculate how much
RAM we need for how much data?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
