Calling any S&M crunchers for Lattice

Good news is there's about 14K in new WU's to be had. Bad news is these Garli's take a lot of CPU time (usually over a day) and memory and the payout is low (ok very low by some standards). I've been hanging in as the WU's trickled out all this year but would like to move on. Trouble is there's too many damn WU's in this batch and with only about half a dozen SUSA members picking up a few we could be at this for awhile. Over all SUSA is doing OK and holding our own in the middle of the pack but is not near any milestones. So if you need/want a personal milestone or if your into S&M at all, Boinc-wise I mean, please fee free to grab a few WU's from http://boinc.umiacs.umd.edu/. :-bd

You know I am always on it, that is when I can actually get WU's.

It's always fun when it downloads 2 tasks and starts them immediately. Then it causes everything else to get compute errors. It wouldn't be so bad if it was easier to limit it to one active task at a time. Once it starts, though, it's a data bomb. I'm trying to get to 50k but it's getting harder and harder with only 4 Gig's of ram.

My cruncher building rule of thumb: Always plan on at least 2gb of RAM per CPU thread.

Unfortunately, I already hit my 1M MM at Lattice. And I already have the GARLI app at 5k hours. If they would only release work fore the other apps!

I suspend all but one Garli WU at a time. It won't download any new WU's when I do this but that's not a big problem. When one ends then I un-suspend the next WU.

I haven't had any issues with Lattice messing up other WU's. At least not on the two or three machines I have it accepting work.

Quote:

---

Originally Posted by trigggl

It's always fun when it downloads 2 tasks and starts them immediately. Then it causes everything else to get compute errors. It wouldn't be so bad if it was easier to limit it to one active task at a time. Once it starts, though, it's a data bomb. I'm trying to get to 50k but it's getting harder and harder with only 4 Gig's of ram.

---

Can you not set it to run only one max_concurrent task at a time using app_config.xml?

Quote:

---

Originally Posted by kmanley57

Can you not set it to run only one max_concurrent task at a time using app_config.xml?

---

I'm pretty sure I tried that or something like that.

WU's are half gone. Thanks to Pwrguru for the assist. BTW: these aren't the really long Garli's, most are being completed in less than 8-12 hours on decent desktops.

Not my favorite project but I wanted to move up a few places...

I am seeing really tiny credit return for some reason.

I hear you Denim. Seems near 700 points is normal for these WU's but you got 73 yesterday and 60 today. You must have pissed someone off. :-). PwrGuru: It's a torturous project in terms of return on time but it's1 of only 2 projects I'm in the top 10 so I have to try and hang on. We all can't be Zombie67. If you hang in through this batch, you might make it to 4th or even 3rd on the team and could then maybe be in the top 100 on the project.

Quote:

---

Originally Posted by NJCaNS

I hear you Denim. Seems near 700 points is normal for these WU's but you got 73 yesterday and 60 today. You must have pissed someone off. :-).

---

Not sure why it is so low, but the run times seem a little shorter. One other thing I have noticed was they were consistent for a few days. Two WU's would finish staggered, then two more would come in. Repeat.

Huge mega silly long run-times now. One WU is one day shy of a month late and has been crunching non-stop on my sole surviving laptop. I have a number of other WU's that snuck in while I was running out of Rosetta and have completely clogged up about 40% of my CPU cores. Never thought I would see a single credit awarded. Yes, just one credit today for lattice, according to WUProp, combined I have something around 1300+ hours pending, and multiple WU's are not even at 50%. Very frustrating, as being from a family full of University of Maryland grad's, it has special meaning to crunch Lattice. Really killed my RAC as of late.

My love for Lattice is almost run out. The erratic run times, some only minutes, some weeks. The tremendous RAM hog, and terrible credit return. I was top 100, and a few times threw everything I had that could hold Lattice, and just kept slipping. I am just sick of how Lattice just hijacks the machine and they are almost unusable if I allow it to run while in use. I have two running now that have over 10 days of non-stop run time and close to 20 days left remaining. The lattice site already said they timed out..... :mad:

This is supposed to be fun, and Lattice is a project that is special to me. But this has been a PITA for 5.5 years.

I was trying to run Lattice before the Pogs challenge, and probably will again once my POGs goal is met, but at the moment I've got zero Lattice WU's onboard, but 2,500+ hours "pending" according to WuProp. There were numerous WU's I cancelled with over 10 days worth of crunching simply because they were still incrementing the time remaining. And I thought I'd seen in the forums that they'd never take more than 10 days. I definitely understand where you're coming from denim, and am amazed at your patience! :))

Quote:

---

Originally Posted by Mumps

I was trying to run Lattice before the Pogs challenge, and probably will again once my POGs goal is met, but at the moment I've got zero Lattice WU's onboard, but 2,500+ hours "pending" according to WuProp. There were numerous WU's I cancelled with over 10 days worth of crunching simply because they were still incrementing the time remaining. And I thought I'd seen in the forums that they'd never take more than 10 days. I definitely understand where you're coming from denim, and am amazed at your patience! :))

---

Thanks. I felt the urge to stay on the project as our team has almost abandoned it for the exact reasons I just ranted about, and that I really wanted to be top 100.