UT theoretical chemistry code forum

Looks like you have an issue with excessive credits, this one for example where the credit is over 97,000 for a single task. There are quite a few of these around it appears.

http://eon.ices.utexas.edu/eon2/workunit.php?wuid=116202146

http://eon.ices.utexas.edu/eon2/workunit.php?wuid=116201847 ...

Actually, the issue is the project doesn't support checkpointing (saving incremental progress to a file). With checkpointing, the project would restart from the last checkpoint it saved if you shutdown, etc. The suspend in memory is fine if you run multiple projects. I think (maybe wrong) that you ...

Actually, what I have observed is that sometimes if you detach and then reattach, the points get better or if you stop working on the project a bit and then start again, they are OK. But return a few days worth of results and suddenly the points drop in half. Really strange.

Well, I suspect you may realize by now, based on the # of computers reported on your project home page, that crunchers would appear to be losing interest in your project due to the low points as there used to be over 800 computers at one point. I have a couple machines that seem to be doing "ok ...

This is basically the same as the disk limit thread. That's what's causing the errors. The errors report something like 10.15MB > 10MB so the computation aborts. Looks like this was introduced in 3.06. Not all WUs reach this point, but most do, so I've set my machines to no new task, but I will have ...

Actually I take that back. It's happening on my Linux machines as well. And it's only recently, so the first batch of 3.06 tasks went fine, its just the latest ones that are doing this. My Mac is still running the 3.05 client, so looks like the Mac client isn't updated to 3.06 yet.

Same here, but looks like its only my Windows machine. I was completing a bunch of 3.06 tasks, but then it just started happening. I complete an occassional task though. So not all tasks are hitting the projects internal 10 mb file limit.

I have a Windows 7 64-bit machine, several Linux machines and a Mac working part-time on this project. The Windows 7 one is producing considerably less points than the others for the amount of CPU time, so it would appear the credit calculation issue is with the Windows version. I have set it to no ...

Yep, all my machines are on Linux. All returning results OK, but credit ranges from .01 to .05 per work unit. Really?

Most of mine are not completing now. I have one that has a 1.6GB memory footprint so it has quite a memory leak. Eventually it will go to Waiting On Memory state in the BOINC client and not continue. Several others have done this already and I just have to abort them.

Please post when this issue is ...

I currently have another one that is at about 1.2G and another at 789M. It looks like they just keep growing for awhile and then stop growing at different points. They seem to finish after awhile if you let them go, that is if it doesn't crash your system first. :-)

The new 1.21 client running on 32-bit Ubuntu Linux is taking a large amount of memory. My last result grew until it took 388MB before it finally finished.