Introducing The 64-Bit Mwo Client!
#41
Posted 18 December 2014 - 08:29 AM
#42
Posted 18 December 2014 - 08:34 AM
#43
Posted 18 December 2014 - 08:54 AM
#44
Posted 18 December 2014 - 08:55 AM
#45
Posted 18 December 2014 - 08:59 AM
#46
Posted 18 December 2014 - 09:09 AM
#47
Posted 18 December 2014 - 09:57 AM
#48
Posted 18 December 2014 - 10:24 AM
JHackworth, on 18 December 2014 - 08:55 AM, said:
64bit allow MWO to use more that 4GB of memory which indirectly increases performance because it allow the app to cache more stuff into RAM. The following shows the relative speed of accessing data from various type of memory by translating the times into seconds so you can get an appreciation for the difference in scale between the numbers:
1 CPU cycle---------------0.3 ns--------1 s
Level 1 cache access---0.9 ns--------3 s
Level 2 cache access---2.8 ns -------9 s
Level 3 cache access---12.9 ns------43 s
Main memory access---120 ns-------6 min
Solid-state disk I/O------50-150 μs---2-6 days
Rotational disk I/O-------1-10 ms-----1-12 months
As you can see, putting more stuff into RAM changes the access time to minutes from days or months, relatively speaking. This mean that the app spends less time waiting around for data so it should make things go faster.
#50
Posted 18 December 2014 - 10:44 AM
#51
Posted 18 December 2014 - 10:55 AM
#52
Posted 18 December 2014 - 11:04 AM
Alexander Garden, on 17 December 2014 - 05:30 PM, said:
Your house/apartment/dwelling
Does this mean AMD owners are going to get the shaft again?
#53
Posted 18 December 2014 - 11:21 AM
HARDKOR, on 18 December 2014 - 10:44 AM, said:
If you were to figet with your system you could already use those 8 cores. but now MWO wont use a maximum of 512MB per core for a lame 32bit memory max. instead allowing all your ram to work as win 7(+) 64bit intended . unleashing a bottleneck im hoping........
#54
Posted 18 December 2014 - 11:35 AM
Edited by Celthora, 18 December 2014 - 11:40 AM.
#55
Posted 18 December 2014 - 11:47 AM
#56
Posted 18 December 2014 - 12:03 PM
Both the Xdiag and C++ installs said what was loaded is current or newer than what was downloaded.
Any advise would be appreciated.
Edited by VictusRhul, 18 December 2014 - 12:03 PM.
#57
Posted 18 December 2014 - 12:05 PM
32 Bit:
Max of 4 gb of memory used by the OS + all process
However, you graphics card counted against that memory total, so if you have a 1 gb graphics card you would only use 3 Gb for the processes
64 bit
Home Basic- 8 GB for OS plus all processes
Home Premium- 16 Gb
higher than that 192 Gb
HOWEVER,
when running 32 bit apps, that process is limited to 4 Gb of space. Unlike a 32 bit OS, the graphics card does not count against that limit as long as you have more memory. In addition, iother 32 bit processes (OS, TS, Firefox, etc) can each use 4 gb of space, and 64 bi process can use the entire memory space. this means the 4 Gb is not shared like a 32 bit OS. For this reason 8Gb minimum is your best bet for a 64 bit Windows OS
when running a 64 bit app, the process can utilize all available memory. up to the limits above.
What this means re: 64 bit MWO.
If you have >4Gb memory and a 64 bit OS, AND you are not using all the rest of the memory for your graphics card, the Os, and other process, you should see more memory utilization.
Example: (numbers are made up, but not unreasonable)
8 Gb x64 machine:
Graphics card mapping: 1 gb
OS: 512 Mb
TS: 50 Mb
AV- 25 Mb
other apps- 125 Mb
This leaves 8Gb -1 Gb - 750 Mb = 6,25 Gb free space.
since MWO runs as a single process app,
32 bit MWO can only use 4 gb of the free memory.
64 bit MWO can use all 6.25 Gb of the memory
Edited by Sprouticus, 18 December 2014 - 12:08 PM.
#58
Posted 18 December 2014 - 12:09 PM
XenonCx, on 17 December 2014 - 08:22 PM, said:
chances are that is the newest version that they release and the rest are patched. You probably have all the patches so its not necessary. If you're running windows then you already have the package. That is mainly for people running other OS's like linux or OSX that don't automatically download those as part of the native OS
#59
Posted 18 December 2014 - 12:09 PM
InnerSphereNews, on 17 December 2014 - 05:10 PM, said:
64-bit users running low-spec machines may experience performance issues if attempting to run the 64-bit client. We recommend that those users stick with the 32-bit client if they experience any issues.
Very interesting. This is counter to my experience with 64-bit vs. 32-bit apps in general. Looking forward to giving it a try when I'm home from this stint on the road.
Long time in coming though, well played PGI.
#60
Posted 18 December 2014 - 12:11 PM
5 user(s) are reading this topic
0 members, 5 guests, 0 anonymous users