Re: 32 bit or 64 bit in this situation?




Unfortunately, my chipset supports a max of 4GB and that is what I
have installed. This means that both 32 and 64 bit OSs have the same
amount of memory available, viz 3.12 GB. See MSKB 929605 for more
info.

Are there any performance benefits in this situation to using 64 bits
over 32 bits (Windows and/or Linux)? I am only interested in better
performance and nothing else like driver availability.
--

Since you're only seeing 3.12 GB with a 32 bit OS you would get almost a full gig more with 64 bit. That would improve performance if you sufficiently load the system - you would be able to run more applications before the system would have to start using the page file. An important issue is whether or not the BIOS supports memory mapping above the 4 GB address space. In order for the OS to use all 4 GB for itself and applications the memory addresses for hardware need to be moved up.

.



Relevant Pages

  • Re: xmalloc string functions
    ... require memory allocations depending on the way the system works. ... If the toolkit being used is not one of those, then it is irrelevant that some provide a means to do so, particularly if the "some" are not available for the platform being targeted. ... Not enough context for most real-world applications to recover at this point. ... At this point g_malloccalling abortbecomes a moot point, particularly if your auto-save code is robust against memory allocation errors. ...
    (comp.lang.c)
  • Re: ProDOS Plus
    ... operating system was not considered worth the problems when it was just as easy to make the applications support 128k or more ram. ... your suggested P-code system could do something similar by running in the aux 64k memory range $D000...FFFF or perhaps the aux ram used by the P8 /ram driver code space. ... the OS could fit in *only* the space that ProDOS now occupies. ... if practicality were a concern we probably wouldn't be using old hardware. ...
    (comp.sys.apple2)
  • Re: xmalloc string functions
    ... If these were the only choices (crashing applications or a frozen ... trying to malloc some rediculously large amount of memory - e.g. in the ... because their malloc wrapper decided to exit. ... Exiting on malloc failure makes sense for a utility like sort. ...
    (comp.lang.c)
  • Re: xmalloc string functions
    ... require memory allocations depending on the way the system works. ... Not enough context for most real-world applications to ... It is /more/ reliable to routinely auto-save the user's work (as you ... particularly if your auto-save code is robust against memory allocation ...
    (comp.lang.c)
  • RE: DLLHOST.EXE and Secure Server Crash
    ... This is a very common problem with COM+ components and IIS. ... | Applications view switch to Status View) ... |>with 2-3 dedicated SSL servers. ... A symptom of the problem centers around memory ...
    (microsoft.public.inetserver.iis.security)