Re: MSAS 2gb/3gb limit...

Dave,

Thanks for your response...

I'm sure we're saying the same thing but I just want to clarify, only
because I'm trying to ensure that what I believe to be true is really true.
I'll start off with the definitions that I know:

Private Bytes = Virtural Memory space, physical or (physical + pagefile),
reserved for the given process

Virtual Bytes = Physical Memory or (physical + pagefile)

Working Set = Recently accessed pages in Virtual memory (physical or
(physical + pagefile))

Now my question/clarification… You said that the memory an application can
address is “working set plus page file usage”. My confusion comes from that
I think of Working Set to be the above definition. So I would say that the
total memory MSAS can address, depending if /3GB or /USERVA are used, is
2-3gb Virtual Memory. Am I correct to assume that?

Again, I apologize if I’m splitting hairs… It’s just that some of our
systems require that level of tuning and I just want a reality check.

Thanks…




"Dave Wickert [MSFT]" wrote:

> In operating system terms is it "virtual address space". So you are right,
> it is really working set plus page file usage.
>
> In practical terms, it also relates to recommended physical memory used by
> AS.
> This is because Windows as an operating system doesn't really like to page.
> It has the provision but you won't get peak throughput from the system if it
> does a lot of paging.
> --
> Dave Wickert [MSFT]
> dwickert@xxxxxxxxxxxxxxxxxxxx
> Program Manager
> BI Systems Team
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "BATMAN" <BATMAN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:22646394-2268-426B-A36E-FCD55C8EB372@xxxxxxxxxxxxxxxx
> > Thanks for the response.
> >
> > To be more specific. What I'm asking is if the MSAS 2/3gb limit (3gb with
> > the /3gb switch in the boot.ini) is related to only physical memory or
> > total
> > virtual memory. Virtual being (physical + pagefile). For example, if
> > MSAS
> > consumed 1.5 physical and .5 paging file, would MSAS be at it's max?
> >
> > Thanks again!
> >
> >
> > "Darren Gosbell" wrote:
> >
> >> The 2/3 Gb limit (depending on how your boot.ini file is configured)
> >> affects the total addressable memory space. So that probably be what you
> >> mean when you say virtual memory.
> >>
> >> That is, if you have a 32bit box with more than 3Gb of physical RAM AS2K
> >> can still only address (use) a maximum of 3Gb.
> >>
> >> The only way to get over this limit is to use a 64bit operating system.
> >>
> >> The other thing to note on this is that for the dimension cache, AS2k
> >> can launch a separate process called VLDM (very-large-dimension-manager)
> >> that can give you an addition 2Gb of memory for large dimensions at the
> >> cost of some performance for inter-process communication.
> >>
> >> --
> >> Regards
> >> Darren Gosbell [MCSD]
> >> <dgosbell_at_yahoo_dot_com>
> >> Blog: http://www.geekswithblogs.net/darrengosbell
> >>
> >> In article <E1A4F4BA-7843-46DC-98B1-A53ABDF6EA6D@xxxxxxxxxxxxx>,
> >> BATMAN@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> >> > Is the 2gb/3gb limit physical memory or virtual memory?
> >> >
> >> > Thanks
> >> >
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: If Macs have no spyware....
    ... >had made a complete code review of its operating system and removed all ... and writing new data into those memory locations would ... >but when the data exists on the stack, it can cause very large problems. ... >location that needs to be written in place of the correct execution ...
    (comp.sys.mac.advocacy)
  • Re: If Macs have no spyware....
    ... First you yammer about being a Mac advocate, then bad mouth me for dumping XP in favor of a Mac. ... Supposedly Microsoft had made a complete code review of its operating system and removed all the buffers which could overflow. ... the fundamental problem is that the basic architecture of Windows has two fatal flaws in its memory management and while these remain in the software the ad hoc patches will never be enough to make Windows a secure operating system. ... These problems are bad enough when dealing with data in the one routine but when the data exists on the stack, it can cause very large problems. ...
    (comp.sys.mac.advocacy)
  • Re: virtual memory
    ... you can have virtual memory ... that software transparent swapping requires virtual memory. ... (since swapping it into physical memory is all or nothing). ...
    (comp.arch.embedded)
  • Re: Why is VS 2005 so slow?
    ... You are confusing physical memory with virtual memory. ... Note also that the number of apps you can run at the same time doesn't change. ...
    (microsoft.public.vc.mfc)
  • Re: [Lit.] Buffer overruns
    ... > floating point support or a memory expansion option. ... had virtual memory support grafted on. ... > where the modified instruction was fetched from. ... vis-a-vis the official coporate strategic operating system TSS/360. ...
    (sci.crypt)
Quantcast