open All Channels
seplocked Macintosh
blankseplocked Is it possible to assign more RAM to eve application
This thread is older than 90 days and has been locked due to inactivity.

Author Topic

Templar Knightsbane
Posted - 2011.06.08 20:24:00 - [1]

Edited by: Templar Knightsbane on 09/06/2011 02:16:02
When im running eve, and looking at my activity monitor, it consistenly says that eve is only using like 2.4gb ram or thereabouts, but it also says that 2gb of ram are free, which really, i would like used on eve to try and speed it up, as thats what i have bought extra ram for right??

is this possible, or is there a reason there is 2gb RAM unused???

Ps - z run 5mb in total

da go
Posted - 2011.06.09 05:04:00 - [2]

EVE is a 32 bit process. It has a grand total of 4 GB of virtual address space. Everything is to be mapped in that space. Under standard windows OS such a program will have 2GB for his own code and his own data and 2GB for mapping the operating system calls and any DLL (shared library) code it loads. That's why the memory size of the EVE process, as reported by OSX, is generally somewhere between 2 and 3 GB effective.

When there are bugs in EVE that result in memory leaks, that size will start to grow indefinitely up to when the process eventually crashes with an out of memory exception. When that happens the effective size reported by OSX for EVE is somewhere between 2.7 and 3 GB.

It's not OsX that refuses to allocate memory to EVE. It's EVE that refuses to ask for more memory (and it couldn't ask for much more even if it wanted because it wouldn't be able to map it to any of its virtual addresses anyway).

As far as OsX is concerned, it will allocate to each process as much memory as that process will ask. Even more than is physically available. It's in fact easy to write a program (a 64 bit program, of course) that requests 100 GB of memory. And OSX will comply. Just make sure you have sufficient space on your HD for the swap file and do not be surprised when the system basically stops responding for several minutes. It will work, but very very slowly.

Templar Knightsbane
Posted - 2011.06.09 15:09:00 - [3]

er, ok

so i should leave that then and is working how it meant to be

im not a coder or anything, just seemed odd that half my memory was free, but u have explained it to me,

is there anything else that can be done without programming to speed eve up in osx?


da go
Posted - 2011.06.09 18:16:00 - [4]

Originally by: Templar Knightsbane
is there anything else that can be done without programming to speed eve up in osx?
There isn't much to do. Not even programming, as the only ones that can write code for EVE are Transgaming and CCP.

Not having other programs in the background helps.

Having RAM and VRAM in a cleaned state when starting EVE helps a lot. Logout and then log back in to OsX to start with a cleaned state.

Periodically clear your EVE cache (especially after a client update).

A lot of time is spent by EVE accessing the disk. This is particularly true for the upcoming incarna client, especially when docking. Using a 5400 rpm disk (typical of laptops) is very detrimental. Conversely an SSD disk is going to help a lot.

Configure EVE for performance, use a sensible overview setup, remove brackets.

Rogue 2
Posted - 2011.06.09 18:28:00 - [5]

If you're running on a 64-bit system w/ 12Gb RAM, will EVE be able to use a full 4Gb?

da go
Posted - 2011.06.10 03:44:00 - [6]

Originally by: Rogue 2
If you're running on a 64-bit system w/ 12Gb RAM, will EVE be able to use a full 4Gb?
As far as OsX is concerned, the memory management part of the kernel has been 64bit for ages. So 64 bit applications can allocate whatever they want.

Unfortunately EVE is a 32 bit application, therefore it will never be able to map more than 4 GB of address space.

Furthermore EVE is developed for Windows and Cider provides EVE with a windows-like API and environment. That means that the client cannot allocate more than about 2GB for private data and 2GB for system and shared data.

This is not an OsX problem nor a 32 bit application on OsX problem. It's EVE itself that will not allocate more than that. (reason: it is a 32bit windows application and those are the limits it would have if it was running on Windows, therefore it just does not try to allocate more).

As I wrote in a previous post, in the past we have had bugged clients that would leak memory (that is they kept allocating memory until they crashed with an out-of-memory exception). They crashed with an active footprint of about 3GB. That's when the windows emulation failed to map more addresses. The "missing" 1GB is most probably due to the fact that, under windows, application addresses and system addresses are separate but all mapped into the same 4GB space, so it capped out the application address space and crashed even if there was still space in the system address pool.


This thread is older than 90 days and has been locked due to inactivity.


The new forums are live

Please adjust your bookmarks to

These forums are archived and read-only