64 Bit Processors (was "System Out of Memory " - but is it really...? " 2004-01-27 - By Shawn Bogart
Back
Couple of things here. One, currently there is only a beta version of WIN64
for the AMD processors, so the version that HP is shipping is the same ole
version that we all have. Won't due squat with the extra 32 bits. Second, an
application either has to be re-written from the ground up to take advantage
or a 64-bit OS or it has to have extensions added to it to take advantage of
a 64-bit system. Just like every consumer version of Windows did until XP.
(NT doesn't count) And it's gonna be a LONG time before you start seeing
your favorite apps re-written as 64-bit. My guess is that we won't see
anything other than a couple of "show piece" apps with 64-bit extensions
(except for photoshop) until Intel ships a 64-bit processor AND Microsoft
ships a full 64-bit OS. And given where both of these giants stand right
now, I'd say we've got a solid 2-3 years before we see anything major. Just
remember, the 386 chips came out back in 89', but it wasn't till XP that we
got a version of Windows for everyone that was completely a 32-bit OS.
AMD has a nice piece of "test" hardware out, but marketshare is what it's
all about and AMD doesn't even come close to having enough market share to
really swing everyone to 64-bit processors. Remember, Alpha's have been
64-bit since 92' and we're all running those, right?
Hope that helps some,
Shawn Bogart aka, SiSiX
sisix@(protected)
www.sisix.net
-- -- Original Message -- --
From: "Dave Angelini" <dpangelini@(protected)>
To: "Shawn Bogart" <shawn1@(protected)>; <truespace@(protected)>
Sent: Tuesday, January 27, 2004 9:35 AM
Subject: 64 Bit Processors (was "System Out of Memory" - but is it
really...?")
> I've noticed that HP is beginning to sell consumer PC's with AMD's
Athlon's
> 64 bit series of processors. While these processors have slower clock
> speeds (2.2 GHz), the bandwidth increase should more than make up for it.
>
> So while this type of processor should handle more memory intensive
> applications with ease, the question which I have is with reference to the
> OS. HP is selling this processor with the standard Windows XP Pro OS.
>
> Is XP Pro optimized for 64 bit processors? I am sure it can run on a 64
bit
> processor (otherwise HP would not allow this configuration) but I fear
that
> it will run as a standard 32 bit application.
>
> Next question is: If these processors are starting to make their way into
> the consumer world, how long do you think until our favorite applications
> start to be re-written for 64 bit systems? Do applications need to be
> re-written or will a 64 bit OS manage the bandwidth change.
>
> Thanks,
> Dave Angelini
>
>
>
> -- -- Original Message -- --
> From: "Shawn Bogart" <sisix2@(protected)>
> To: <truespace@(protected)>
> Sent: Tuesday, January 27, 2004 2:24 AM
> Subject: Re: [TSML] "System Out of Memory" - but is it really...?
>
>
> > You're getting this message because Windows cannot access all of the
> memory
> > that you're trying to have it use. I hate to say it, but you're scene is
> > just too big. That's why a lot of the real complexe scenes that you see
> have
> > to be composited. In effect, you're trying to tell a 32-bit OS to use
> > 33-bits of memory. (32-bits = 4GB of RAM. Windows NT/2000/XP can only
> access
> > 2GB for an application.) I would look and see what it is in your scene
> that
> > is taking up so much memory and then try to parse it back some.
Eliminate
> > some geometry that you don't need or cut back on some of your textures.
> > Additionally, the resolution that you are rendering at will make a HUGE
> > difference when the amount of memory to render is being considered.
> >
> > Hope this helps some.
> >
> > Shawn Bogart aka, SiSiX
> >
> > sisix@(protected)
> > www.sisix.net
> > -- -- Original Message -- --
> > From: "Kris" <pterochromics@(protected)>
> > To: <truespace@(protected)>
> > Sent: Sunday, January 25, 2004 3:13 PM
> > Subject: [TSML] "System Out of Memory" - but is it really...?
> >
> >
> > > Hello!
> > >
> > > I'm trying to render a scene that's 168MB in size. I set up a Swap
file
> > > that's 4GB in size and have 1 GB of RAM. I also have RamBooster
> running.
> > >
> > > WHen I try to render the scene, I get "Out Of Memory" system boxes pop
> up,
> > > usually 4 one right after the other. I close the boxes.
> > >
> > > RamBooster is showing that the RAM percentage-used bar does
> > > fluctuate. Also, the Swap file has never gotten over about 1.7GB in
> size,
> > > IOW, not even half the capacity has been used.
> > >
> > > As an experiment, I'm leaving the system running after having closed
the
> > > message boxes.
> > >
> > > What I'm wondering is:
> > > (1) why does tS generate Out Of Memory warnings when it hasn't used
more
> > > than 1/4 to 1/3 of the RAM *or* the VIrtual Memory (swap file)?
> > > (2) Should I let the thing continue running in the hope that it will
> > > eventually render after a few days, or is tS just dead in the water
> > despite
> > > the changes (according to RamBooster) in the %age of RAM used?
> > >
> > > Thanks In Advance :) !
> > >
> > > - Kris M. Krieger
> > > http://www.pterochromics.com
|
|
