I've done everything to enable the use of more than 2GB memory for AS 2000 according to http://support.microsoft.com/kb/295443
Still, according to the task manager, the process msmdsrv.exe stops growing around 1 996 000 kB.
I've added the /3GB in boot.ini and set the Memory Conservation Threshold in Analysis Manager to 2.7 gb.
I've also checked that the HighMemoryLimit was set accordingly in the registry.
OS: Windows 2003 server Enterprise Edition
Memory: 3 GB
AS2000 sp4
Any other settings/limitiation I've missed?
Actually, later today the memory usage finally past 2GB, obviously it wasn't needed until then. I stayed at 1.9 so long even though users were querying it heavily so I thought it didn't work. Thanks, and sorry.
One related follow-up question though: when AS gets out of memory while processing cubes it automatically reboots and we get the "Connection to server is lost" when the transaction is to be commited. Will the same thing happen if AS reach the memory limit while users are querying the cube? Will the service be rebooted and queries be aborted, or will it just show as worse performance for the users? Or will AS free up memory automatically when we're getting close to the memory limit?
|||Server restart is not a normal thing. During commit though, when it half-way through commiting, and there is any kind of error happening (like out of memory), it can no longer go back, but it cannot leave transaction half-commited either. So AS simply restarts, and finishes commit on restart. This kind of restart won't happen if out-of-memory happens during querying.
No comments:
Post a Comment