i do not know if this helps but i had some similar problems the last days and lost also wu's, einstein and gpugrid. On my side it was a problem with the virusscanner ( i hope ), made an update to the newest version, big mistake. Pagefile is growing all the time and the available memory is shrinking, nothing to see in the taskmanager, everything is looking ok for the processes. After deinstalling the new version it looks good again, at the moment i run a test with an older version of the scanner and startet gpu crunching on einstein also. At the moment the pagefile is not growing and no shrinking of the avaiable ram.
I think tomorrow i know if it was the virusscanner, but at the moment it looks like.
Greetings Rabbit,
I just checked my virus scanner software and I haven't had a major program upgrade since August, just the engine and signatures have been updated regularly. So, I don't think that that is the problem. Thanks for the suggestion! :)
Keep on BOINCing...! :) (I'm limping along for now!)
After all that, I fired up task manager to observe the performance graphs. The page file usage was over 5 GB and my available physical memory was at about 4 MB, this with only 4 VP WUs running! After a few minutes everything mellowed out to just over 2 GB page file usage and 1.6 GB available physical memory.
Ok, now I'm really confused! I just looked at my VP WUs and they're barely over 100 bytes each! And still, a great deal of physical memory is being used. And not only that, I'm still getting "Waiting for memory" messages!
Now I'm really baffled! I have never had this much problem with BOINC before, not even on the past, less powerful PCs I've built. At least not that I can remember. I have 2 WUs running and 2 "Waiting for memory". I still show 1.6 GB available physical memory. Why would a 100 byte WU need to be waiting for memory!?
Keep on BOINCing...! :) (I'm trying already!!!)
VirtualPrairie uses an extraordinary amount of RAM, users report 500MB+ with a full 1GB per core/task regarded as required for smooth running.
(My small laptop system already gets sluggish with only one core on VP)
see this (and surrounding posts) and this from the VP forum.
So, if your problems with Einstein are based on memeory issues, running VP will produce similar problems.
Carola
-------
I'm multilingual - I can misunderstand people in several languages!
Ok, now I'm really confused! I just looked at my VP WUs and they're barely over 100 bytes each! And still, a great deal of physical memory is being used. And not only that, I'm still getting "Waiting for memory" messages!
And what would the task size have to do with the amount of memory used? I can write you a small program that uses all of your machine's memory.
By the way, the actual Einstein (S5) tasks are also only a few bytes. What takes so much disk space are the (semi) permanent data files.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Ok, here's what I have done and what I will be doing. I am determined to get to the bottom of this.
[ WHAT HAS BEEN DONE: ]
1. I have finished all WUs for all BOINC projects. All projects are set to NNT.
2. I have been working with the Computer Management program in Windoze. All devices are working properly. I looked at the system log in Event Viewer and found only one error which I deduced to be minor. No other errors or warnings after last re-boot.
[ WHAT I WILL DO: ]
1. The i7 will be running without BOINC for a few days or so.
2. I will do my normal daily activities on the i7, less BOINC.
3. I will occasionally monitor my system event log for any anomalous entries.
4. If I see any anomalous entries in the system event log, I will research those errors/warnings on Micro$oft's website through the link provided in Event Viewer.
5. If I see no anomalous entries after, say, 2 or 3 days, I will restart BOINC and allow VP to run.
I believe that by following the above plan, I will narrow down the problem I am experiencing. I still say it's strange that this should all start when I restart crunching Einstein. Perhaps BOINC got corrupted somehow. At any rate, I feel I will get to the bottom of this, once and for all.
Thank you all for your suggestions and support. I really appreciate it! :)
Keep on BOINCing...! :) (I'm on hold for the time being. Actually, my Linux box is still crunching SETI. :) )
Something else you may want to add to your to-do list: memory checks.
If the problems manifest themselves when lots of memory is being used, it can also be that one or more memory sticks have damage in the higher memory ranges.
Just run memtest86+ for a day on that machine. If it survives that, you're 99% sure it ain't the memory. Since computers are finicky things, keep a 1% option it is memory. ;-)
Something else you may want to add to your to-do list: memory checks.
If the problems manifest themselves when lots of memory is being used, it can also be that one or more memory sticks have damage in the higher memory ranges.
Just run memtest86+ for a day on that machine. If it survives that, you're 99% sure it ain't the memory. Since computers are finicky things, keep a 1% option it is memory. ;-)
Greetings Jord,
That was the first thing I did this morning, just not all day. I forgot to mention using memtest86.
When windows bugs out, doing a 'fix' isn't always a good idea. Sometimes it's like trying to put a band aid on cancer, you are better off slicking and reinstalling.
You said you had like 172 tasks to report. What about changing your setting to something like only keep 0.2 days worth of work on your system, so that way you are not loading up a huge potential workload and pretty much get a new one as you finish an old one. If you find you are having comm problems then there isn't a bunch of stuff piling up on you.
Just a suggestion.
Thanks for listening.
Aaron
If god meant for us not to BOINC he'd have made our #$%^%^ shorter!!
RE: Hi, i do not know if
)
Greetings Rabbit,
I just checked my virus scanner software and I haven't had a major program upgrade since August, just the engine and signatures have been updated regularly. So, I don't think that that is the problem. Thanks for the suggestion! :)
Keep on BOINCing...! :) (I'm limping along for now!)
CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187
Siran's website: [ ONLINE! ]
RE: After all that, I fired
)
VirtualPrairie uses an extraordinary amount of RAM, users report 500MB+ with a full 1GB per core/task regarded as required for smooth running.
(My small laptop system already gets sluggish with only one core on VP)
see this (and surrounding posts) and this from the VP forum.
So, if your problems with Einstein are based on memeory issues, running VP will produce similar problems.
Carola
-------
I'm multilingual - I can misunderstand people in several languages!
RE: Ok, now I'm really
)
And what would the task size have to do with the amount of memory used? I can write you a small program that uses all of your machine's memory.
By the way, the actual Einstein (S5) tasks are also only a few bytes. What takes so much disk space are the (semi) permanent data files.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Are you meaning the Ackermann
)
Are you meaning the Ackermann doubly recursive function? It eats all the memory of any computer even for a couple of small integers.
Tullio
Greetings all, Ok, here's
)
Greetings all,
Ok, here's what I have done and what I will be doing. I am determined to get to the bottom of this.
[ WHAT HAS BEEN DONE: ]
1. I have finished all WUs for all BOINC projects. All projects are set to NNT.
2. I have been working with the Computer Management program in Windoze. All devices are working properly. I looked at the system log in Event Viewer and found only one error which I deduced to be minor. No other errors or warnings after last re-boot.
[ WHAT I WILL DO: ]
1. The i7 will be running without BOINC for a few days or so.
2. I will do my normal daily activities on the i7, less BOINC.
3. I will occasionally monitor my system event log for any anomalous entries.
4. If I see any anomalous entries in the system event log, I will research those errors/warnings on Micro$oft's website through the link provided in Event Viewer.
5. If I see no anomalous entries after, say, 2 or 3 days, I will restart BOINC and allow VP to run.
I believe that by following the above plan, I will narrow down the problem I am experiencing. I still say it's strange that this should all start when I restart crunching Einstein. Perhaps BOINC got corrupted somehow. At any rate, I feel I will get to the bottom of this, once and for all.
Thank you all for your suggestions and support. I really appreciate it! :)
Keep on BOINCing...! :) (I'm on hold for the time being. Actually, my Linux box is still crunching SETI. :) )
CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187
Siran's website: [ ONLINE! ]
Something else you may want
)
Something else you may want to add to your to-do list: memory checks.
If the problems manifest themselves when lots of memory is being used, it can also be that one or more memory sticks have damage in the higher memory ranges.
Just run memtest86+ for a day on that machine. If it survives that, you're 99% sure it ain't the memory. Since computers are finicky things, keep a 1% option it is memory. ;-)
RE: Are you meaning the
)
I didn't have any specific function in mind. Actually, it would be enough to just fill the complete memory with some constant values.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: Something else you may
)
Greetings Jord,
That was the first thing I did this morning, just not all day. I forgot to mention using memtest86.
Why only 99%? Why not 99.9% or 99.99%? ;)
Keep on BOINCing...! :)
CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187
Siran's website: [ ONLINE! ]
RE: Why only 99%? Why not
)
'Cause you're not cheap. :P
When windows bugs out, doing
)
When windows bugs out, doing a 'fix' isn't always a good idea. Sometimes it's like trying to put a band aid on cancer, you are better off slicking and reinstalling.
You said you had like 172 tasks to report. What about changing your setting to something like only keep 0.2 days worth of work on your system, so that way you are not loading up a huge potential workload and pretty much get a new one as you finish an old one. If you find you are having comm problems then there isn't a bunch of stuff piling up on you.
Just a suggestion.
Thanks for listening.
Aaron
If god meant for us not to BOINC he'd have made our #$%^%^ shorter!!