The problem is you may still be in the effected group with regards to the "storm warnings" about HCC. There was a "small craft advisory" post a while back, but this wouldn’t effect you. But as I was inspecting problems with the duo's here, I noticed that I was dropping more than points, but hours as well.

When I got HCC work units, my life here seemed to be shrinking. Part of it was the slower machines here were crashing and some small power outages that would bias the score, but there still was a discrepancy.

I was going through some contortions to try to make my systems more stable and bring up more units, when I ran into some "back alley" conversations that would back up what I'm seeing. That multi-core machine should steer clear or batten down for heavy weather. In your case even more so, Xeon single core machines may show signs of slowing. Some best describe this slowing as a memory allocation “leak”, but the problems with any of this is the reputability of the source of info. So there is no way for me to directly relieve the problem except to post a warning.

A warning that I don’t want to post. As like you, my roots are in Grid.org.

Well Seke you should just keep checkin my stats graphs, lately WCG is getting 5% more share and my time is continously reducing, could you pls explain that then?
I am thinkin on leaving this project as I am trying to contribute more and more resources into it and results show: I am returning results with errors on the same PCs that do not err on other projects, time is reducing while in reality it is increasing, my clients are freezing lately for no reason, but for sure only when running WCG tasks.

This is what I think of WCG Sekerob: I think you don't care about the people conributing notable resources to this noble project, by not repairing errors as they appear, only when you see a reasonable CPU time lost all over the project. This is why UD went down in the first place.

I guess you can see the graphs yourself, they are downhill lately! You can also see a bunch of dumped or erroneus results appear in a short period of time. Would I be careless enough just to let my PCs do the work and sit back, you wouldnt get any feedback. All my agents would just hang there doing nothing!

This is my problem, that wcg people do not want people talking about problems, because it means there ARE problems. This is something that drove people here from GRID.org, the lets make em shut up way! By creating a real support, not a forum, but a support page, where I could read where I can find those logs that you are talking about, maybe WCG could really get what they want. They would get loads of crap that they made by being not thorough enough on the testing cycle and if they answer, they wouldnt have to be looking on the forums for trouble!

Let's not forget who is paying for those CPU cycles!

Sek,

As the thread this post refers to infers, the problem is "quietly" looked into. The problem at this point is not the tech issue that may be causing what we are seeing, its what can we do to effect what ever this issue is on our end.

Pepe,

What I'm trying to do in these posts here is to prevent the problem you are facing. What I have done with the machines I have here, is to find out "what hurts". So far, if I remove the multi-core machines and anything below 1ghz, like pc100's, I run fine. Also note that Cargod is running fine and he it running strickly HCC. The reason is he runs 1.8 to 2.4ghz single core machines. Thus further backing my claim. But this claim is not one I want to be bringing a bunch of attention to. For in the end, the un-do chaios could become much worse that the primary issue that could be causing this in the first place.