Problem

-- what is happening when executing searches on a large amount of Message Log entries ?
-- how the memory is handled when using Copilot ?

Resolution

* when running a search in Message Log :
    -> a dat file is created under $CORE_DATA/tmp file. dat file size depends on on the results returned by the search. make sure you have enough disk space before launching a search returning a large amount if entries
    ex : 100 000 entries may create a dat file > 500Mo file (but it depends on the type of events)
    the file is removed when you close the search result
    -> memory used by the sysman process (under r4edi) increases.
    ex : a search on 100 000 entries may consume around 200Mo memory (it depends also on the type of events)
* memory used by the sysman process increases also when opening Copilot tools like Task Monitor, Queue Monitor (several Mo per tool)
* a sysman process consuming several hundreds of Mo is not unusual on a loaded environment
* a monitoring of the sysman process is recommended on a production environment
* process is stopped and memory is released when closing the Copilots