15 réponses à ce sujet

[Skepticck]

Don't know if anyone else got this issue but here goes.

I have Win7 32bit and my memory usage is around 800- 900 MB with only windows running.

So, i already had Origin installed but it was an older version, when i started it today to download ME3 demo it updated to a newer version, i downloaded and installed ME3 from Origin and played the demo.
After quitting the demo and Origin i noticed that the memory usage was higher that it is usually (it was now ~1.3GB), so i tought maybe Origin or the game didn't properly release the memory after quitting so i restarted windows and got 1.2 to 1.3GB usage with only windows running.

My memory usage never been this high with only windows running so i don't know what Origin installed but something was using a lot of memory and it is something that doesn't appear in Task Manager because the processes displayed are the same ones that are usually there.

So i uninstalled ME3, completely uninstalled Origin, restarted windows  and now i'm back to 800 to 900 MB usage like before, so does anyone else notice this and can someone from Bioware or EA explain what Origin or ME3 installes that uses so much memory When Origin and ME3 are not even running.

[Unit-Alpha]

Origin uses up to 150MB on my system, not that much, but it's still 5 times more than Steam does.

[wolfsite]

On my System Origin is about 110 K Memory Usage steady.

Steam tends to jump around with me but it can go from 75K to 165 K

[Skepticck]

Of course programs use memory when they are running, what i wrote is that memory is still used for something EVEN after Origin is closed and after i restarted the computer, so something is using ~300 to 400 MB more than my normal usage, something that after i uninstalled Origin and ME3 demo is not there anymore.

[moddingy]

Origin is currently using 853,372 K memory while idle on my computer. I'm pretty sure the current release has a memory leak.

[DHJudas]

Don't set origin to start when your computer starts... that's a first step.

2nd is that after running origin it uses about 150mb give or take as most people are seeing.

Additionally, 32bit mostly a dead OS now, 64bit has been available for 10 years, in computer terms that may as well be a century. And it's been widely supported for over 5 years too.

There is one thing about todays computer world.... that hasn't occured ever before in the computer system industry that i could find.... and that is that it's the first time computer have been able to run and for essentially nearly no money worth mentioning.... A LOT of physical ram, ram isn't much of a concern today. You can get single stick of memory that more than twice exceed the amount that 32bit windows can even see let alone use.... just one.... and they aren't that expensive. It's not at all uncommon to see 2x4gb (8gb) kits floating around for half the cost of what ME3 does. Top it off if you have windows vista or windows 7, you already own a 64bit OS.... just download the oem or retail version of the windows OS (this is legal) and burn it.. install 64bit using your current cd key and be amazed..

BTW if your running 4gb of ram on a windows 32bit os, you do realize you have 256mb through to as much as all of it totally unavailable depending on the size of your video card.

Nowadays... those with 1gb Video cards (common) have access to 2.75GB of ram with 4gb of ram installed.. meaning you've paid for 4gb... but 1.25gb of it isn't useable..... therefore wasted.

Crossfire with 2x 1gb?.. lol 1.75gb of useable physical ram..... basically below recommended requirements of the game.

[moddingy]

@DHJudas You're computer requires a 64-Bit capable CPU to function properly with a 64-Bit Operating system. It isn't uncommon for someone to have a computer that does not support it. In fact a few companies such as Dell and HP still produce 32-bit computers.

[Hackrus]

Not to mention, that x64 systems does not work properly on some C2D / C2Q processors because of known issue with EM64T implementation (and a lot of people does use these CPUs).

Also, you guys should know that most of current games - including Mass Effect games series - are in fact 32 bit applications and as you know, x64 Windows systems can allocate only something about 2GB of physical memory for these applications, in exceptional cases 3GB (if they are well programmed).

[DHJudas]

moddingy wrote...

@DHJudas You're computer requires a 64-Bit capable CPU to function properly with a 64-Bit Operating system. It isn't uncommon for someone to have a computer that does not support it. In fact a few companies such as Dell and HP still produce 32-bit computers.

Aside from a select few netbooks that are no longer being sold.... no.... they don't sell 32bit only machine for the past 5 years.

intel and AMD cpu's have had 64bit support since more than 5 years ago.

AMD's launch of the x64 compliant Athlon series cpu in 2002/2003 and intel's late to the game (due to their own 64bit version blowing up in their faces and then essentially stealing/copying)..

Many of the later D series pentiums and ALL of the core duos and later intels have 64bit support.

Intels Atom 4xx series started to show x64 support. Recently i've installed x64 on a few netbooks.

A Large amount of the laptops have supported x64.. and netbook/laptops were the last to migrate. in 2005 AMD was doing exceptionally well with the turion x2 cpu which was 64bit compliant.... interestingly, i've a nearly 8 year old laptop sitting right beside me sporting this cpu running windows 7 x64 with 8gb of ram.... got to love a low-mid range laptop sporting the amd cpu and ati x1xxx series gpu that still works great and supports the amount of ram that exceeds it's specifications just fine.

Even some smartphones are now running x64 compliant hardware.

x64 has become a REQUIREMENT.... if you don't have it.... it's almost a guarantee that you'll be running into issues.

And if your planning on gaming, it's most definitely needing it unless you plan on sticking to video games that aren't modern.

Like the 16bit to 32bit move...... its pointless to argue and defend an obsolete and dead standard.

[DHJudas]

Hackrus wrote...

Not to mention, that x64 systems does not work properly on some C2D / C2Q processors because of known issue with EM64T implementation (and a lot of people does use these CPUs).

what are you talking about..... there are no issues with the 64bit implementation for opperating x64 windows on the C2D or newer cpu's.... considering i've ran all flavors of them for years and i'm typing this message out using windows 7 x64 on one of the earliest C2D on the market without a hitch, the performance improvement over 32bit is considerable.... many of those initial "issues" have been resolved with patches/fixes implemented years ago...

Also, you guys should know that most of current games - including Mass Effect games series - are in fact 32 bit applications and as you know, x64 Windows systems can allocate only something about 2GB of physical memory for these applications, in exceptional cases 3GB (if they are well programmed).

You better re-read, you got that ENTIRE thing backwards... you should have said 32bit windows NOT 64bit.

Almost all applications are 32bit apps, majority of games, only 32bit windows systems can allocat 2gb TOTAL virtual memory (includes physical ram) to any specific program. The only exception is 3gb IF you enable the PEA + 3g switch in windows 32bit however this has very BAD effects and is actually counter productive.

Windows 64bit systems grant each individual 32bit program it's own 4gb limit, meaning you can run dozens upon dozens of 32bit programs.... and neither one of them will effect the others ability to have access to their own COMPLETE 32bit pool of memory.... ZERO limitations.

The 32bit program however MUST have Large Address AWARE enabled by default.... Luckily Bioware wasn't stupid and made this function enabled by default for Mass Effect 2.... This is why ME2 is considerably better at loading/faster on a windows x64 machine then running under a windows 32bit system.

[Hackrus]

DHJudas wrote...
what are you talking about..... there are no issues with the 64bit implementation for opperating x64 windows on the C2D or newer cpu's.... considering i've ran all flavors of them for years and i'm typing this message out using windows 7 x64 on one of the earliest C2D on the market without a hitch, the performance improvement over 32bit is considerable.... many of those initial "issues" have been resolved with patches/fixes implemented years ago...

Re-read again what I wrote. I said that there are complications with x64 systems on SOME C2D / C2Q processors (it's piece by piece). And are you sure that there isn't any issue with EM64T implemenation at these processors series? Do yourself a favor and check Intel's errata, before you start claiming that. Will give just a hint: EM64T implemenation issue was fixed with newer processors generation Core iX.

And one more thing: I am not saying, that C2D / C2Q aren't 64b processors. They are. What am I saying is, that they are not fully compatible with x64 architecture and sometimes this issue is causing instability at x64 systems (and no, you cant fix that by using newer BIOS, etc., and no, problem wasn't solved..).

That means - x64 systems may and also may not run on these CPUs. Nothing more, nothing less.

DHJudas wrote...
Almost all applications are 32bit apps, majority of games, only 32bit windows systems can allocat 2gb TOTAL virtual memory (includes physical ram) to any specific program. The only exception is 3gb IF you enable the PEA + 3g switch in windows 32bit however this has very BAD effects and is actually counter productive.

Windows 64bit systems grant each individual 32bit program it's own 4gb limit, meaning you can run dozens upon dozens of 32bit programs.... and neither one of them will effect the others ability to have access to their own COMPLETE 32bit pool of memory.... ZERO limitations.

The 32bit program however MUST have Large Address AWARE enabled by default.... Luckily Bioware wasn't stupid and made this function enabled by default for Mass Effect 2.... This is why ME2 is considerably better at loading/faster on a windows x64 machine then running under a windows 32bit system.

Well, you got this right - I agree that I made few misteps here and there. Well, I guess nobody is perfect and we're still humans after all

[DHJudas]

Hackrus wrote...

DHJudas wrote...
what are you talking about..... there are no issues with the 64bit implementation for opperating x64 windows on the C2D or newer cpu's.... considering i've ran all flavors of them for years and i'm typing this message out using windows 7 x64 on one of the earliest C2D on the market without a hitch, the performance improvement over 32bit is considerable.... many of those initial "issues" have been resolved with patches/fixes implemented years ago...

Re-read again what I wrote. I said that there are complications with x64 systems on SOME C2D / C2Q processors (it's piece by piece). And are you sure that there isn't any issue with EM64T implemenation at these processors series? Do yourself a favor and check Intel's errata, before you start claiming that. Will give just a hint: EM64T implemenation issue was fixed with newer processors generation Core iX.

I'm well aware of the original implementations of EM64T in the first series of C2D and C2Q, some of the functions were disabled while running in this mode which would result in "slower" performance but this was negated by the much faster 64bit instructions. Overall the performance value was improved.. just not as much... Stability was an issue initially but indeed bios updates and later revisions were able to disable the "extra" functions that made the stability problematic.

As i stated, the EIST function that was initially "enabled" by default with EM64T would produce the stability problems your talking about... and indeed a bios update WOULD resolve it by FORCING this function off allowing EM64T based solutions to work just fine.

I'm using the first EM64T based intel CPUs on the market today withe 64bit windows with zero issues or stability problems at all.

[Hackrus]

Well, in my own experience on some processors was simply impossible to run x64 systems. And no, BIOS updates did not solved this. Done with this - I do not want get mods angry because of useless spam in this thread. We may continue in personal messages if you want, but as I see it, we both have different experiences.

[moddingy]

DHJudas wrote...

moddingy wrote...

@DHJudas You're computer requires a 64-Bit capable CPU to function properly with a 64-Bit Operating system. It isn't uncommon for someone to have a computer that does not support it. In fact a few companies such as Dell and HP still produce 32-bit computers.

Aside from a select few netbooks that are no longer being sold.... no.... they don't sell 32bit only machine for the past 5 years.

I stand corrected.

[BongMong]

It is worth noting that Win Vista/7 does not use memory like Win XP did. Why leave memory empty when you can cache? It's just a waste. With proper memory management you can stop. worrying about clearing out stuff from RAM.

[MegumiAzusa]

Hackrus wrote...

DHJudas wrote...
Almost all applications are 32bit apps, majority of games, only 32bit windows systems can allocat 2gb TOTAL virtual memory (includes physical ram) to any specific program. The only exception is 3gb IF you enable the PEA + 3g switch in windows 32bit however this has very BAD effects and is actually counter productive.

Windows 64bit systems grant each individual 32bit program it's own 4gb limit, meaning you can run dozens upon dozens of 32bit programs.... and neither one of them will effect the others ability to have access to their own COMPLETE 32bit pool of memory.... ZERO limitations.

The 32bit program however MUST have Large Address AWARE enabled by default.... Luckily Bioware wasn't stupid and made this function enabled by default for Mass Effect 2.... This is why ME2 is considerably better at loading/faster on a windows x64 machine then running under a windows 32bit system.

Well, you got this right - I agree that I made few misteps here and there. Well, I guess nobody is perfect and we're still humans after all

Not quite, 32 bit programs on Win7 64bit can still use more than the 4gb, the 32bit limitation is only when you allocate a single block. For example the Command and Conquer World builder splits its buffers in 8MB parts, doodleing around with it (editing some game files, adding assets, etc) created a real usage of >8GB (got 16GB installed)