Applies to SnapCenter Server 4.6 and 4.6P1 Issue Over time, the SMCore Service on the SnapCenter server is increasing in memory usage without releasing it again. Noteworthy is the usage of frequent cl...Applies to SnapCenter Server 4.6 and 4.6P1 Issue Over time, the SMCore Service on the SnapCenter server is increasing in memory usage without releasing it again. Noteworthy is the usage of frequent clone information retrieval either via REST-API or via Powershell (i.e. Get-SmClone).
Depending on the pmap version the end output would summarize, for example, where the second total is the RSS (in-memory) value and the extra output even shows shared memory: Note: The default heapspac...Depending on the pmap version the end output would summarize, for example, where the second total is the RSS (in-memory) value and the extra output even shows shared memory: Note: The default heapspace seetings are 2GiB for the SPL service (main access point on port 8145, includes SCU and SCO functionality), 1GiB for the SCC service which handles both SCHANA and SCC Creator plug-ins, and 512MiB for the SCC Watchdog process, for a maximum heapspace usage of 3.5GiB of RAM.