ok.
It would go in which portion of disk.
I mean where the stardog server is installed or disk space where stardog_home resides.
Actually in my case, stardog install disk and stardog_home are at different disk.
I don't know exactly but I'm fairly confident it doesn't go in the install disk. I think it would be either STARDOG_HOME or TMP or whatever you've setup temp to be if you didn't go with the system default.
I have checked, memory rss is occupied in RAM not in disk.
But why it is going beyond specified memory?
as you ca see.
[shishir18106@compute-0-2 ~]$ free -g
total used free shared buff/cache available
Mem: 94 46 11 0 35 46
Swap: 29 25 4
this is free memory in my system.
RSS is all the memory used by the Stardog server process, it includes both Java heap and offheap memory. If you allowed 12G for heap and 16G for direct memory, then 19G RSS is within limits.
Under certain workloads Stardog can go a bit beyond limits (for example under writes) or when certain background processes run (e.g. data compaction).
Memory issues during querying are most likely related to having no statistics and thus suboptimal query plans.