Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 6
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 956 times and has 5 replies Next Thread
my090007
Cruncher
Joined: Aug 8, 2005
Post Count: 17
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
angry Yes, but what about the agent HANGING ONTO physical memory ???

Yes, I too have this problem with memory. I've read all the posts re: CPU usage etc. But I have found that when the agent runs, first, it grabs a chunk of physical memory. When I'm using my machine, sure, the agent doesn't run BUT it doesn't let go off the memory. when it runs again, it ADDs another chunk and so on. Soon, it is HOLDING onto a large chunk of physical memory - (and there's 1.2GB of the 1.8 GB of virtual memory FREE) - and my system is running like a dog. I'm running Win XP on a ThinkPadT41 (1.4 Ghz, 768MB RAM) and I don't think the system's configured wrong. if ANYONE can help me with any pointers, it'd most appreciated.
[Dec 22, 2005 2:32:54 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
confused Re: Yes, but what about the agent HANGING ONTO physical memory ???

Hello my090007,
You are the second person reporting this (well, a similar) problem on their computer that I have heard of. Last week Rick Alther asked that person:
If you see this happening, we need to know the device ID it occurred on as well as the time it was running on that device (anytime will do while it was running). This allows us to go back and look up the specific workunit and look at it in more detail.

This is needed to check out the particular work unit on our machines. But it seems to happen repeatedly to the same people, which would not be the case for bad work units. Therefore, I hope you will give us complete information about your system. Belarc Advisor is a good diagnostic tool to identify your software environment.

mycrofth

Added: The other case grabs 287 MB physical RAM and never lets it go down into Virtual Memory. Your case sounds much worse.
----------------------------------------
[Edit 1 times, last edit by Former Member at Dec 22, 2005 3:37:48 AM]
[Dec 22, 2005 3:34:23 AM]   Link   Report threatening or abusive post: please login first  Go to top 
my090007
Cruncher
Joined: Aug 8, 2005
Post Count: 17
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Yes, but what about the agent HANGING ONTO physical memory ???

Ah, right, mycrofth. Thanks. My device ID is IBM-MY090007. Altho', after watching it like a hawk for the past week, and reporting it today, the agent seems to have been a bit more circumspect !!! It's hanging onto only about 50Mb - it was growing upto 100 last night.
[Dec 22, 2005 7:42:26 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Yes, but what about the agent HANGING ONTO physical memory ???

hey, one of mine is a t41 also! smile but i've never had that problem.
[Dec 22, 2005 8:22:44 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Alther
Former World Community Grid Tech
United States of America
Joined: Sep 30, 2004
Post Count: 414
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Yes, but what about the agent HANGING ONTO physical memory ???

Ah, right, mycrofth. Thanks. My device ID is IBM-MY090007. Altho', after watching it like a hawk for the past week, and reporting it today, the agent seems to have been a bit more circumspect !!! It's hanging onto only about 50Mb - it was growing upto 100 last night.

The Fight AIDS @ Home workunits allocate just over 300MB of VM and actually use 75-100MB of that (physical RAM). This is normal. The very begining of the workunit (the first few minutes), the numbers will be a bit lower.

If you see a workunit using more than 120MB of physical RAM, please jot down the device ID and the time it was running at and we can take a look at the specific workunit.
----------------------------------------
Rick Alther
Former World Community Grid Developer
[Dec 22, 2005 2:41:02 PM]   Link   Report threatening or abusive post: please login first  Go to top 
my090007
Cruncher
Joined: Aug 8, 2005
Post Count: 17
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Yes, but what about the agent HANGING ONTO physical memory ???

OKay. So, perhaps I've got under the collar too soon ? !! Thanks, and I'll check elsewhere to see what else is holding the hsow up. Ta.
[Dec 23, 2005 7:31:23 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread