I have optimized apps running and after waiting 24 hours due to trashing a lot of work units with a stupid mistake in app_info, I finally got some more.

However only to find that they got aborted (error -6) as all being VLAR, so I am now waiting another 20 hours to actually (hopefully) get some more work.

Keeping the cpu's busy doing Rosetta while waiting.

Not wanting to sound harsh but that is a little long to wait twice in a row when all I am doing is using an app designed to cut down on VLAR's slowing the hell out of my computer which is CUDA enabled.

---

You waiting twice just because you didn't do backup and not disabled network access for BOINC when starting to mess with app_info.
So you just pay for own mistake IMO. Task trashing could be avoided.

I know that is was my fault for a stupid mistake but the period of waiting should be a lot less, I fixed the app_info and then got new work but your VLAR killer optimized app then trashed the 5 workunits I just got after fixing the app_info.

No one likes VLAR's but they are part of the project and can't be helped, it is more the fact that 24 hours seems a long period to wait when all the work available can't all be VLAR, it was more making a point of the time period is a little long.

I fully accept that it was my causing the problem but in future developments couldn't more of a distinction be made prior to work being sent out as VLAR? something on the server side for example, VLAR's should be spotted earlier in my opinion.

I am in no way mocking the project, they guys do a fanastic job with what they have to deal with hardware and software. Raistmer, your optimized apps have helped a great many people who can't do VLAR units, I can but they slow my GPU down too much if assigned to that. CPU is no so much of a problem. It is only since I have started to actually do CUDA work that things have slowed somewhat on my machine.

Keep up the good work Raistmer and everyone who develops BOINC, APPS or the project admins.

---

(AP Wire 0hr 2min ago.)

Thread Halftime Report

This thread has earned a FLR (Forum Lurker Rating) of 5 out of 5.

A potentially boring subject has blossomed into something bigger than life.

We laughed, we cried, we shared a lifetime. A lack of banishments disappointed the crowd, but payoff came in the form of a few personal blacklistings. Things slowed down a bit mid-half, until Blurf brought us back to our feet with a yellow flag and an admonishment.

Even the productivity rating was high, with the thread resulting in more than one email and phone call to project developers.

All-in-all, a perfect first half!

i do not know what vlar is, nor do i care, i just crunch what ever they toss to my pc, no matter how long it takes. but i did notice that many people were really helpful but they were deliberately ignored, that is what i didn´t understand.

I fully accept that it was my causing the problem but in future developments couldn't more of a distinction be made prior to work being sent out as VLAR? something on the server side for example, VLAR's should be spotted earlier in my opinion.

Yes, it would be perfect solution but not in our scope.
Look earlier in this thread for script that reassign work from GPU to CPU and vice-versa. It should solve VLAR problem + increase host performance.
Will create separate thread for it soon.

i do not know what vlar is, nor do i care, i just crunch what ever they toss to my pc, no matter how long it takes. but i did notice that many people were really helpful but they were deliberately ignored, that is what i didn´t understand.

Ditto ... Although I did venture into the optimized apps venue and now have 2 computers crunching away work units in about half the time or better than before thanks to those really helpful people.