Thanks Andrew. I checked the trap folder and it`s empy. The log file contains only few errors and warnings, but I guess only suppor can say if these are bad.
I`m aware that having too much data in terms of nodes, events, etc.. could cause issue, but we don`t have that many. About 300 nodes and I`ve setup events older than 2 weeks to be deleted.
After restart it behavious propely (taking only 1 or 2 GBs) until I decided to crete a colletion based on attributes. It eat the entire memory for just half a minute, but during that time SIM did not show the attributes I can filter on. Now when it took the whole memory and I want to create new collection based on attributes, I can immediatelly filter by attributes.
So I guess after I want to do something which involves dynamic information, I have to restart the service..
