Jump to content
Eternal Lands Official Forums
bkc56

Memory footprint increased

Recommended Posts

I've had a couple clients open much of the day (one on main, one on PK) and their size in the task-manager was in the 40K range. I started another client on main and noticed it was running around 200K (this was after I'd made some el config changes (changing the max food level)). After trying various things, I restarted the other client on main - it too jumped to the 200K range. So then I tried restarting the PK client (which had no changes) and it too jumped.

 

Now I suppose one possibility is that the client always starts high, and drops over time as it frees up stuff. But I've never seen that. My experience is that the more you play (especially map changes) the larger it grows.

 

There haven't been any Windoze changes (no updates or anything like that).

 

So I'm at a loss as to why the client appears to have had a 5x size increase during the course of today.

Share this post


Link to post
Share on other sites

if I remember correctly, memory use increases as the client reads more textures.

on windows, if you minimize an application, the operating system will swap out the memory it is using.

Share this post


Link to post
Share on other sites

Well I never minimize my clients (unless it's an accidental click) so that doesn't explain the size, but...

 

If I minimize the client it's space drops down to <30K, and slowly climbs as I switch maps.

 

I wonder if there's some other way to trigger it freeing space besides minimizing. That could explain what I see.

Share this post


Link to post
Share on other sites

Im having the same problem, this has only started happening the last 3 days. I also run 2 clients all the time no problems and when i log them on it usually takes a few mins to settle down. Now they both run 200k in the task manager eating all my cpu usage making it near impossible.

 

Unfortunatley i know very little about computors so if anyone can tell what the problem could be it would be appreciated.

 

Davy

Share this post


Link to post
Share on other sites

I've confirmed this happens on two different computers (so it's not related to one specific configuration). Both computers run Win-XP, one being up-to-date on Windoze updates, the other being months behind. Different networks, different hardware, etc.

Share this post


Link to post
Share on other sites

Anyone know if this is happening on Linux or any other varieties of Windows?

 

Lately, my EL client could be in console mode and my computer still ends up running the fan all the time. It is a laptop, so I know that there are some factors else than EL that could cause this, but still I have to wonder.

Share this post


Link to post
Share on other sites

For reasons I forget, I've been monitoring EL client memory usage on my desktop (Running 64-bit Linux) for a year or two. I have an hourly job that records the memory footprint of any running el process (using /proc/<pid>/statm in case you are interested). Below are the figures from some random sessions over approximately the last three versions. As you may expect, I'm usually running the latest dev code so these are not precise release snapshots, more the overall trend. The numbers are in pages (4096 bytes) and the columns after the date are explained in the text below. As already mentioned, the client memory usage grows as you load more data (changing maps etc). Who know what I was going for these sessions. IMHO, there is not much change in memory usage.

 

size total program size

resident resident set size

share shared pages

text text

lib library (unused in Linux 2.6)

data data + stack

dt dirty pages (unused in Linux 2.6)

 

Sat Dec 11 23:17:04 GMT 2010: 205055 53115 7405 777 0 146761 0

Sun Dec 12 00:17:02 GMT 2010: 217829 66378 8014 777 0 159023 0

Sun Dec 12 01:17:02 GMT 2010: 218460 67574 8538 777 0 159142 0

Sun Dec 12 02:17:02 GMT 2010: 218844 68567 8539 777 0 159526 0

 

Mon Jul 4 19:17:23 BST 2011: 192664 54848 6906 616 0 151962 0

Mon Jul 4 20:17:06 BST 2011: 192817 55192 6919 616 0 152115 0

Mon Jul 4 21:17:06 BST 2011: 192817 55198 6919 616 0 152115 0

Mon Jul 4 22:17:10 BST 2011: 193850 64708 7445 616 0 152636 0

 

Sat Mar 10 16:17:08 GMT 2012: 199527 59825 7562 594 0 157955 0

Sat Mar 10 17:17:12 GMT 2012: 199527 59825 7562 594 0 157955 0

Sat Mar 10 18:17:07 GMT 2012: 199527 59858 7563 594 0 157955 0

Sat Mar 10 19:17:10 GMT 2012: 199463 59824 7320 594 0 158147 0

Edited by bluap

Share this post


Link to post
Share on other sites
I have a feeling that those memory problems are display driver bugs.

Could be, but it would be a pretty large coincidence to see the same problem on multiple computers with different video cards (and therefore different drivers). And then to have the same action (minimizing the window) have the exact same effect (size goes down) in all cases. It just seems unlikely.

 

I wish I could still test the previous client and see it's behavior.

Share this post


Link to post
Share on other sites
I have a feeling that those memory problems are display driver bugs.

Could be, but it would be a pretty large coincidence to see the same problem on multiple computers with different video cards (and therefore different drivers). And then to have the same action (minimizing the window) have the exact same effect (size goes down) in all cases. It just seems unlikely.

 

I wish I could still test the previous client and see it's behavior.

 

You can still start them and compare the initial memory use without logging in.

 

What memory value are monitoring? The most important are:

 

Memory - Working Set

Amount of memory that is currently loaded in RAM. This value does change if memory pages are loaded from swap or moved to swap space if they are not in use. Some data like textures may be swapped out if the client is minimized and not rendering anything.

Memory - Commit Size

Total amount of virtual memory that has been reserved by the process. This includes memory mapped files and video memory.

 

http://windows.microsoft.com/en-US/windows-vista/What-do-the-Task-Manager-memory-columns-mean

 

Share this post


Link to post
Share on other sites
Memory - Working Set

Memory - Commit Size

Win-XP's task manager doesn't have those. It has:

  • Memory Usage
  • Peak Memory Usage
  • Page Faults
  • Virtual Memory Size

I'd be happy to take some measurements if I know just what numbers to capture.

Share this post


Link to post
Share on other sites
Memory - Working Set

Memory - Commit Size

Win-XP's task manager doesn't have those. It has:

  • Memory Usage = Memory - Working Set : current amount of RAM used
  • Peak Memory Usage = Memory - Peak Working Set : highest amount of RAM used
  • Page Faults = roughly : number of pages (4k blocks) that had to be read from swap file
  • Virtual Memory Size = Memory - Commit Size : total amount of memory allocated including swaped out memory

Share this post


Link to post
Share on other sites
  • Memory Usage = Memory - Working Set : current amount of RAM used
  • Virtual Memory Size = Memory - Commit Size : total amount of memory allocated including swaped out memory

OK, so these two are the ones you asked for above. It it would be useful for me to capture those two values at startup (before login), after login, and after minimizing (when it drop again)? Those should be pretty easy to capture and post.

Share this post


Link to post
Share on other sites

OK, here are the numbers collected from 4 spots: before and after logging in, then minimized/maximized.

 

State     | Mem Usage | VM Size
----------| ----------|--------
Login     | 158,844   | 427,148
Started   | 172,828   | 438,120
Minimized | 8,408     | 438,296
Maximized | 12,876    | 438,304

I guess the implication is that the program size is 400K+, and the amount RAM resident starts large and drops when minimized.

Share this post


Link to post
Share on other sites
Guest
You are commenting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoticons maximum are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×