I have no data for this project but I did find that Rosetta seems to give points based on time and floating point MIPS (Whetstone) per CPU which it finds in in client_state.xml from <p_fpops> and <p_iops>. When you do a Boinc benchmark it stashes it there.

WCG seems to assign credits per job regardless of time.

It's written up in the hardware forum over there.

WOW that is quick. So I guess, unless you are on the top, you are SOL

I'm trying to figure out how Denis counts points vs WCG vs Rosetta as per my 5950x thread in WCG. I recognise your name and moniker.

Dear all,
Sorry for not notifying you, but last week it was vacation at the university and I couldn't send work. There are times that even in those periods I am attentive, but this time it was not possible.
I'm going to post-process the previous results now and probably this afternoon (it's 10:30 here in Spain), work will appear again.

I don't know how long this has been going on...but I finally had a chance to check my stats in BOINC and saw the line going down, plus in my profile, I have all 0's for tasks.

That does not reflect my experience. My experience is that Denis goes up and down so sometimes I have none, and sometimes I have huge number of Denis tasls in my machine. As far as credits are concerned, in the last month the curve for Denis has gone up from 5000 to 5300; a small increase. My WCG has given a consideral increase but with much more variability than Denis. I have received no work at all on my Linux machine since last June for ClimatePrediction.

DENIS always (since I added it in October last year) had bursts of several 100,000 of WUs available, which is followed by several days of no new WUs at all, apparently until all outstanding WUs have been returned.
Right now, it seems that there have been no new WUs for the last two days now, and with the weekend already started in Spain/Europe, I don't expect another heap of new WUs showing up until Monday morning (my time, I am on the US West Coast, that's GMT-9 compared to Spain). Though it had happened a couple of times that there was a refill of WUs over a weekend...
Right now, one of my hosts is just crunching on the last DENIS WU (a slow i7 laptop) while another mobile i7 has 37 WUs left in the queue, which are currently just "ready" as they are due on the 31st and another project has some WUs that were on the back burner and are now due by the 30th...


Ralf

I live in Europe. We all take this Monday off as a holiday after Easter Sunday. So I doubt Jose will be releasing anything Monday. Maybe if he has new work,Tuesday sometime.

I don't know how long this has been going on...but I finally had a chance to check my stats in BOINC and saw the line going down, plus in my profile, I have all 0's for tasks.

That does not reflect my experience. My experience is that Denis goes up and down so sometimes I have none, and sometimes I have huge number of Denis tasls in my machine. As far as credits are concerned, in the last month the curve for Denis has gone up from 5000 to 5300; a small increase. My WCG has given a consideral increase but with much more variability than Denis. I have received no work at all on my Linux machine since last June for ClimatePrediction.

I should reactivate the different social profiles, at least for this situations.

DENIS doesn't have nearly the number of folks WCG SUPPOSEDLY has. It's a small project in terms of resources. Keep that in mind. The irony is that Jesus is quick to respond to things as soon as he aware of them. I have let him know a few times when the project was down for an extended period and he's been pretty quick to take care of things once he received the message. He's also been fairly responsive to inquiries in the forums.

I still run a little WCG, although since they keep running out of work or it's allocated to other OS, my systems don't hit them often. It use to be my main project as cancer is a close to home interest. But it's all turned out too little too late. The icing on at all is turning down volunteers and then be unable to report in / respond to the volunteers.

I am getting a sporadic supply of work units, but that is pretty much expected from this project. At least they have a server status page. The supply from WCG is adequate for the moment. At least they seem to have a handle on the assimilation side. I have seen my numbers go down about 10,000 or so. They are making progress.

I have about 300 awaiting validation here which is a little bit higher than normal after a bit crunching, but I have seen the number slowly decreasing, probably until they dump another big batch into the system.

Cheers

on WCG...did you read their tweet from last week?
Basically on a wild guess it will be the end of the month or later before they are back.

I have over 130 wus to report and some news will be welcome during these down

Server status pages update only every so often for BOINC projects, it's not continuous.

Every day, your project is down for hours shortly after midnight.

Today, there was a database error for at least 7 hours.
Remember how you crashed the entire system several years ago without being able to recover it fully with results & stats being partly lost?
You need to thoroughly check what is going on there - just a friendly reminder...

No, most of the invalid causes are problems due to differences in the OS we have no considered. We need to still improve the program to avoid them.

Best,
Jesús

this is an issue with BOINC RPC protocol
if certain packets get lost in transit, the server has sent the tasks to the client and records that fact, the client never got them so they don't show up, and the protocol issue is that there is no acknowledgement to cope with the data loss
i believe there is a server option to resend lost tasks, but that it has been known to be awkward, so it isn't widely used
the "workaround" is just to wait until the server expires them and resends the tasks

This sounds plausible. Remote Procedure Calls (RPC) often use User Datagram Protocol (UPD) which which broadcasts packets and doesn't care if they get to where they should go. It's a well know tradeoff in the IP portion of TCP/IP.

23:00 UTC is about the time they shut down each day for a while so likely an artifact of that.
ISTR uploads complete during downtime but reports/requests get 3600 second backoff.

Just noticed this morning (Pacific Time) that the web site shows almost 40 WUs, send out on 11/24 23:04UTC for this particular host (Windows 10) as "In progress". However, no such DENIS WUs are actually showing up in the Tasks list of the BOINC client (yes, it is set to show "all" tasks, and it shows task from another BOINC project).

Any ideas what is going on?