UT theoretical chemistry code forum

I will second this and add that the benchmarking is also a little off, to the point where running eOn on a modern i5 or six-year old P4 gives the same estimate of 300+ hours til completion, where it really takes one to two hours.

But yep, definitely a deadline thing. Since they don't actually take ...

21502715 30650128 3522 7 Jan 2011 7:37:35 UTC 7 Jan 2011 12:55:19 UTC Completed and validated 8,436.80 2,515.77 13.19

Geez, never mind. Ok I'm pulling that machine from eOn. Nearly 2.5h for 13 credits is pointless. I'll just stick with my i5 laptop doing the same exact tasks in (this is ridiculous ...

Actually, I take that back (sorta). One of my XP boxes is now showing time estimates of over an hour per task and is running eOn as "high priority," meaning everything else gets shunted off the CPU. Tad annoying, that. I'll see how many credits I get for those, but geez, I hope it doesn't take an ...

Hm...my two 64-bit OS X machines are completing WUs between 430 and 600 seconds (i5 and C2D), and my two 32-bit Windows XP boxes are doing them in upwards of 3000 seconds (Pentium 4), but I'm getting no more than 5 credit each.

So from my point of view, nothing's changed about credits. These aren't ...

Ah...infinite loop. Long timescale dynamics. Haha.

Well okay - glad it's not the client. Seems like there has been a new client version every couple of days recently. Good thing it's not an issue with having developed them too fast or something like that.

Thanks for the update.

Same problem here.

The 727560067-xxxxx WUs seem to run indefinitely. One had run for two hours and the progress bars all read 0.000%. I've suspended the project because there's definitely something wrong with the new client.

OSX 10.6.5 on Intel i5, by the way.

New client's progress bar is kinda cool. Also - really glad you fixed the issue with 139xxxxxxxxx WUs not working on OSX. Takes about a minute for me now, and no computation errors.

Everything's very smooth and crunching well - nice work, and thanks.

Right...it's not a Windows problem with those 139######## WUs. I too mentioned that my XP machine crunched (crunches) them fine.

No it is not fixed. I still get computation errors.

Thu Nov 4 14:24:24 2010 eon2 Starting 1391006163_633_10415275_0
Thu Nov 4 14:24:24 2010 eon2 Starting task ...

I was about to make a post identical to Slave_Mac 's. Just so we know it's not an isolated incident, I too am having problems where all 139###### workunits result in immediate computation errors due to absent output files, a problem similar to that exhibited by the i386 MacBook running Tiger which I ...

Ah ok, so it wasn't just me. I had the same thing happen; 4 new tasks every minute to the point where it ran all night and did about 200...now it won't run at all which I'm sure is another issue altogether and probably not a problem serverside, as it now says "this computer has reached a limit on ...

Are you running Linux? It seems this complaint has surfaced before...

I see - thanks chill, good to know.

I understand there's a lot involved in running this project, but we're all pretty eager to crunch for ya - looking forward to getting more tasks as you get more simulations up and running again!

Hi, I'll reuse this thread because it seems silly to start a new one, as I'm sure this is an issue that will be resolved quickly.

I have a 2.53GHz Core i5, so it's got 4 threaded cores and therefore can crunch 4 BOINC tasks at once. Up til recently it was doing this with eOn (and my old Core 2 Duo ...