Hey All,

For some reason I am not getting any return results from the Nbody app. The validator went down over the weekend and caused a huge backlog in the queue. I think this may be the issue as we have had something similar before. I am going to cancel the workunits in the queue and let it refill. If you see anything strange in the next 24 hrs with nbody workunits this is the reason.

Sidd

My node work is not being acknowledged and my avg work number is decreasing. Cycled all my nodes and same result.

I caught the same error messages I found before the bundling remedy. The database server was overwhelmed again, even with bundling. I removed nbody from my active project list in my preferences to avoid complications. One of the high-volume projects (IBM's World Community) had a two-day outage. Those clients running both IBM and milkyway projects got a huge bump in milkyway runtime for a week because IBM gradually "trickled up" the uploaded work for at least three more days. Also, something is unstable in the nbody code. I had to abort a job that ran for over a day while it tied up 44 cores with no discernible progress. Hope this helps.

---

The prior pose recorded 44 cores. I meant 4 cores. My keyboard stutters at times.

---

There should be a problem Inside of the calculation way of Nbody. He cannot be solved

ROAD-MAP GENTLEMEN ! WE NEED A ROAD-MAP FOR THE COMING YEARS. FACEBOOK is RARELY UPDATED. WE CAN DO BETTER WITH THE COMPUTATIONAL EFFORT IF WE HAVE AN AIM. THE TRUTH OF THE MATTER IS THAT FEW OF US HAVE ANY IDEA WHAT RESULTS ARE WE AFTER AND WHAT ARE THOSE GOOD FOR ( SCIENTIFICALLY ).

I meant focus more on P.R. (public relations + AIM)

Ok how about some work units for milkeyway prior to locking up for the weekend??? Please...

Lee