cancel
Showing results for 
Search instead for 
Did you mean: 

7.6 kernel.exe consumes more memory than 7.4

Former Member
0 Kudos

Hello!

After installing version 7.6 on Windos XP I've noticed that kernel.exe process takes 0.5G more of VM size than in version 7.4 with same configuration (950M instead of 450M CASHE_SIZE is 32786).

Why is that?

Thanks,

Anya

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Anya,

you can check the parameter history if there are some other parameters which consume more memory with 7.6 than only the Cache-Size.

You can check the system table allokatorstatistics as well to get more detailed information which component is responsible for the memory allocation.

Hope this will help you.

Regards, Christiane Hienger

Former Member
0 Kudos

Hello!

I set CACHE_SIZE to minimum, but the process still consumes about 600M of virtual memory after restart and with 0% data use and do user activity. I attach select * from allocatorstatistic with most significant entries. All the db parameters are default and I did not find anything after comparing with parameters of old version. Is it minimal requirement of kernel.exe?

Thanks,

Anya

SystemHeap 1013661696 1013661696 0 1408 4 0 0

RTEMem_BlockAllocator 376147968 376147968 376147968 708 20 SystemPageCache 708 20

RTEMem_Allocator 14144304 14159000 14680064 5979 1225 RTEMem_BlockAllocator 26 12

RTEMem_RteAllocator 56866408 56866408 57319424 6002 3106 RTEMem_BlockAllocator 14 0

RTEMem_EmergencyAllocator 0 0 262144 0 0 0 0

SystemPageCache 377151488 377151488 377176064 839 21 SystemHeap 791 0

MsgList_EmergencyAllocator 0 0 65536 0 0 0 0

StackSpace 636485632 636485632 636485632 611 4 SystemHeap 611 4

LVCMem_BlockAllocator 11542528 11542528 11542528 4 0 RTEMem_BlockAllocator 4 0

LVCMem_Allocator_001 2032 2032 1048576 1 0 LVCMem_BlockAllocator 1 0

IOMan_Manager 12304 12304 12304 4 0 RTEMem_Allocator 4 0

FBM_Manager 146704 146704 146704 7 0 RTEMem_Allocator 7 0

Converter_Manager 140232 144648 140232 46 2 RTEMem_Allocator 46 2

Former Member
0 Kudos

Well, I found "leaked" memory.

MAXDATADEVSPACES=250

was replaced by MAXDEVSPACES=250

which apparently consumes a large amount of memory. I lowered it to default 10 and memory usage dropped