Posts by Nelson
|
1)
Message boards :
Questions/Problems/Bugs :
Tasks that Error while computing
(Message 582)
Posted 21 Sep 2010 by Nelson Post: Sorceress I have not lost work from any other project as a result of of the NFS lasievef memory usage. When a lasievef WU is downloaded while another project's WU is running and using a lot of memory the lasievef WU simply starts running immediately, which stops any other WUs (greedy little bugger). The lasievef WU starts off using little memory, the increases memory usage after a couple of minutes and errors out when there is not enough. After that that my other WUs start running again from where they left off, without issue. The lasievef WUs should NOT be forcing other WUs to stop like that, it needs to wait in line like everybody else. The NFS software needs some work to fix this issue. Loseing 2-3 minutes per errored lasievef WU isn't so bad. It's intolerable if it causes another projrct's WU to error out. That needs to be fixed, not ignored! |
|
2)
Message boards :
Questions/Problems/Bugs :
Tasks that Error while computing
(Message 580)
Posted 17 Sep 2010 by Nelson Post: I have also had several work units error out and I think I know what the problem is. I have 1.5G of memory and the only time I get an error processing an NFS work unit is when I have another project's work unit using 600MB or more memory either running or in memory waiting to run. (I have BOINC set to keep work in memory.) This happen when reporting tasks and downloading new work and if I get an NFS work unit it just takes over without regard to the current memory useage or tasks that are running. NFS doesn't wait for other tasks to checkpoint and if the other tasks are using more than 500 or 600MB the NFS work unit errors out within a couple of minuets. It appears that if the NFS software was more polite and aware this problem would go away. BTW: the Lattice Project typically uses over 1.2GB on my machine without any errors. Hope this helps |