On a 32-bit Windows Server 2003 Standard Edition SP2, I'm debating the pros and cons of /3gb + AWE + Locked Pages for SQL Server 2005 Standard SP3 CU4.
The system only has 4GB of physical memory, however the developer's IIS service seems to be causing high page-outs for SQL Server.
The solution must be limited to existing hardware and software limitations. (32-bit OS, 32-bit SQL Server, 4GB of physical RAM). The second challenge is that the server is not domain joined so using local workstation credentials to limit LPIM's scope (A highly recommended configurable option for LPIM) may affect application communication between physical servers.
Thanks to @PaulWhiteNZ's response on #sqlhelp there is some empirical data on the topic.