Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Erland Sommarskog <esquel@sommarskog.se>
Newsgroups: comp.databases.ms-sqlserver
Subject: Re: Memory usage: Working set much lower than Commit size
Date: Tue, 03 Jun 2025 20:44:42 +0200
Organization: Erland Sommarskog
Lines: 8
Message-ID: <XnsB2F3D307742D9Yazorman@127.0.0.1>
References: <20250603115159.77d340c71ff78daa318f55ef@g{oogle}mail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 03 Jun 2025 20:44:42 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="510bc025135ab8c835d9c7b1d1d94842"; logging-data="230280"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18yhxXDxL1vZGHEk4byrPzI"
User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32)
Cancel-Lock: sha1:zT5fgzvVo4hKE47V1WwMX1k8V3M=
Xref: csiph.com comp.databases.ms-sqlserver:2266

Anton Shepelev (anton.txt@g{oogle}mail.com) writes:
> Does it mean MSSQL has allocated 13G of RAM but is using
> only 254M?  Or does the Working set somehow not include a
> lot of RAM that MSSQL is using with /Lock Pages in Memory/
> on?
> 

The latter.