[Asus  Eee Pad Transformer Prime] BarryH_GEG:
In this short post I found, it would appear additional RAM should improve multi-tasking as less processes would need to be killed because the memory limit would be higher. Things like more effective multi-tab browsing come to mind. I'd imagine too that with more processes available, perfromance would seem snappier by being able to just call them rather than have to start or re-start them. UI smoothness is probably the number one ***** in Android.

Short explanation of Android Memory usage for new people

This is by far NOT to be considered ALL of how Android manages memory, just a baseline explanation. You can read further either through xda-developers, or a Google search for Let me google that for you.

If you're coming from a Windows machine, you already know the rule of thumb -- the more processes in the background, the slower the machine -- this is where Linux/Unix differs, and since Android is built on the Linux kernel, it's only appropriate that it manages memory the same way.

When you start Linux, a ton of daemons (of course "ton" could be more or less depending on how many packages you have installed) start and stay in the background. When not in use, these daemons are "sleeping." A sleeping daemon does not actively use memory, but rather occupies a small amount just so it can be woken more quickly. In Windows, all processes in the background are considered active and on the loose.

In Android, it has a built-in mechanism for managing these sleeping processes so that whenever the internal memory reaches a certain low point, the least used process is GRACEFULLY shut down (in it's proper sequence, NOT kicked loose like in task killers). This is why task killers (though in some uses, are useful, if you know what you're doing or if you have something lock up) are not great for Android. These hard-coded killoff points are already in there, but their set from the manufacturer pretty low, so doing a multitude of things and multitasking even though it won't freeze the device, will make it slow because there's clutter in there not being used.

Autokiller (root required and free from the market) allows you to adjust these killoff points using presets. You don't need to have an in-depth working knowledge of what you should set for each parameter, just choose a preset. Android will still boot with it's factory defaults, but Autokiller will start automatically and re-adjust them to the preset you chose.​

---------- Post added at 08:49 AM ---------- Previous post was at 08:36 AM ----------

That's the thing I don't get. As a X-Mas gift, I can see the logic behind having to have a Prime now. Or if for whatever reason, you're buying your first tablet and also need it now. For everyone else, it's not like the Prime's going away after the first batch is produced. I went through something similar with the SGS2 when it was launched in May but only because I had a week left to return a phone I'd already purchased within its remorse period. And being first with a shiny new toy is always cool but, by waiting, there's a chance that later produced Primes will benefit from manufacturing changes. You might not have to deal with some of the issues being reported on early units and perhaps get it with ICS pre-installed. My SGS2 was the **** for a couple of months but other dual-cores started to come out and today it's just another phone. In a couple of months the Prime's going to be just another second-gen tablet.