I'm doing a performance test on a high traffic (16000+ users, estimated 1000+ concurrent at peak) Microsoft Dynamics database.
The server has gone on line a few months ago, and I'm doing some tests to see how it is handling the current traffic.
While checking some performance counters during business hours I came across an oddity in the target and total server memory.
While I would only flag this as being an issue if the target memory was clearly higher than the total memory, combined with perhaps other counters (depending on the amount of difference) the results here are somewhat odd.
SELECT object_name, counter_name, cntr_value FROM sys.dm_os_performance_counters where (object_name like '%Buffer Manager%' and counter_name like '%page life%') or (object_name like '%Memory Manager%' and counter_name like '%memory grants pending%') or (object_name like '%Memory Manager%' and counter_name like '%target server memory%') or (object_name like '%Memory Manager%' and counter_name like '%total server memory%');
I came to the following results:
counter_name | cntr_value ------------------------------------------------ Page life expectancy | 14887 Memory Grants Pending | 0 Target Server Memory (KB) | 44040192 Total Server Memory (KB) | 44040184
Clearly there is currently no memory pressure, and the page life expectancy is higher than required. However it looks like at some point the sql server was exactly 8 KB short of memory.
Something about these numbers seems odd to me, but I can't put my finger on it.
Is this an indication that at some point the sql server was on the verge of a memory problem?
Am I correct in thinking that because these numbers are so similar, I can dismiss it for now, and test again when a decent amount of time has passed?