Re: User Memory Quotas

From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 12/24/04 

Date: Thu, 23 Dec 2004 16:33:31 -0700

That is exactly the got ya here. AFAIK the limit is hard-wired
and was set back when memory was much more limited and
expensive, and when systems were single user machines.
The issue is how many winstation desktops are there on your
running system as it seems you may need to increase this
(or to figure out why the app is consuming so much heap and
adjust design so objects are released at earliest opportunity)
but that increase in size of each impacts the total number of
allocations you have available. I would be glad to find out
there is a doc'd way to adjust this 48 meg size, but I have not
run on that info. 

-- 
Roger Abell
Microsoft MVP (Windows  Security)
MCSE (W2k3,W2k,Nt4)  MCDBA
"Bodger" <jbrown@jlbprof.com> wrote in message
news:1103841900.970701.219820@c13g2000cwb.googlegroups.com...
> Hmm, something bothers me.  Although this is likely our problem, it
> seems hard to believe that their is a fixed size "system wide 48 mb
> buffer" that all desktops are allocated from.
>
> Can this 48 mb buffer be increased?
>
> I am afraid if I tinker with it, some of my services will not properly
> run.
>
> Thanx
>
> Julian
>

Relevant Pages

  • Re: User Memory Quotas
    ... "Roger Abell" wrote in message ... > adjust design so objects are released at earliest opportunity) ... > allocations you have available. ... >> buffer" that all desktops are allocated from. ...
    (microsoft.public.windows.server.security)
  • Re: Problem with linked list
    ... !pool and see what piece of memory has ... allocated (thankfully you tag your allocations). ... > The buffer is filled the following way: ... >> what's in the section of MYSTRUCT (which you don't appear to have ...
    (microsoft.public.development.device.drivers)
  • Re: Fast way to allocate buffer for producer/consumer scenario
    ... queue and triggers another thread to handle the received data. ... What I now did was to restructure this so that instead of copying the buffer ... VirtualAllochowever interoperates with the OS to reserve pages in virtual and physical memory, which in itself presents an overhead. ... However, I think you'll get the biggest benefit by using a "small buffer" optimization, where smaller allocations are held directly in the object and therefore copied rather than moved. ...
    (microsoft.public.vc.language)
  • Re: Multithreaded File Writes
    ... 7K puts you at nearly 2 gigs of allocations when processing all of your files. ... Drop a smaller buffer in place to lower your mem requirements ... Do your profiling first, figure out where the idle time is going, then work on ... > What is the CPU doing when its idle and there is no disk activity. ...
    (microsoft.public.dotnet.framework.performance)
  • Re: + or += (was: why not use i++ instead of ++i in for()?)
    ... > reallocate the buffer and copy l again, ... > Best case, three temporaries on stack, but no allocations. ... times plus one assignment, ...
    (microsoft.public.vc.stl)