Whoa, the large F@H units really suck up memory...

[InlineFive]

I have a large three-four day, 6xx point unit running and it's using 105MB of memory! :Q That's a bit crazy...

-Por

 

[natethegreat]

I am mostly new to this so I have a question for you🙂 How do you determine the ammount of memory your current project is using?(my current project is #1134) I am running winXP home SP2 if that helps

 

[superkdogg]

Ctrl-Alt-Del. Processes. Memory usage is listed along with CPU usage.

 

[InlineFive]

Originally posted by: natethegreat
I am mostly new to this so I have a question for you🙂 How do you determine the ammount of memory your current project is using?(my current project is #1134) I am running winXP home SP2 if that helps

You probably won't be using up that much memory if you don't allow the client to download work units greater then 5MB. That option is in the configuration under the connection tab.

And if you want to do that depends on your system speed and how much memory you have. I have 1.5GB so it's no major hit, but I'm used to things like Lifemapper that use up 8MB. 🙂

 

[natethegreat]

so 89,316 K = 89 MB I have 1 GB of 2700, installed F@H as a service, and using -advmethods, -forceasm. Is this pretty much all I can do?

Thanks for the quick replys everyone😀

 

[Insidious]

That's the config I'm using. (you can add the -verbosity 9 switch if you want to see a little more information in the fahlog.txt file.

might want to be sure you answered YES to the large packets question so you will get the big work units.

(you can check by looking at the client.cfg file with Wordpad:

------------------------------------------------

[settings]
username=Insidious
team=198
asknet=no
machineid=1
local=706
bigpackets=yes

[http]
active=no
host=localhost
port=8080
usereg=no
usepasswd=yes

[clienttype]
type=0

[core]
priority=0
cpuusage=100
disableassembly=no
ignoredeadlines=no

-----------------------------------------------

happy folding!

:beer:

-Sid

 

[GLeeM]

Yeah they use a lot of memory. The regular WUs don't use near that much.

That is a big part of the reason they are worth double points!

It's an easy way to double your points per day if your machine has the ram.

@natethegreat
Yep, you're doing great!

 

[ProviaFan]

Something I figured out a while ago is that the memory usage reported next to the core isn't always entirely correct. This can be noted by shutting down the F@H service, opening the task manager, and watching the Commit Charge while the service restarts. This may not be the case in all instances, but it was enlightening to see that what I thought was just a little Tinker using 10MB of RAM, was actually a much larger WU - using around 40MB of RAM IIRC. :shocked: