Does switching to 7.4.44 creates a new computer ID? or you can switch back and forth and it will remain on the same computer ID?
And what is rescheduler?

EDIT: nevermind, found info about the rescheduler, that is the cpu2gpu script right?

---

That's why BOINC 7.4.44 was developed.

Just curisity it still has the 1000 WU limit or that was changed to 3000?

Are you asking about 7.4.44 or 7.8.3? 7.4.44 has the 3000 limit and 7.8.3 still has the 1000 limit.

. . While we are getting just 3 to 4 hour outages that is a moot point :) ... touch wood ... (puts hand on head)

Stephen

:)

Does switching to 7.4.44 creates a new computer ID? or you can switch back and forth and it will remain on the same computer ID?
And what is rescheduler?

EDIT: nevermind, found info about the rescheduler, that is the cpu2gpu script right?

. . That is the version by Laurent, it works well for me ... There are others too, such as Jeff Buck's very nice effort.

Stephen

. .

No, installing any version of BOINC never creates a new host ID. In the case of TBar's BOINC versions, it is as simple as copying five files into the BOINC directory to change versions and then restarting BOINC.

That is one of the reschedulers. There have been several over time from Mr. Kevvy's GUPPIRescheduler to W3Perl's cpu2gpu to Jeff Buck's GUI rescheduler.
I have made all of the reschedulers available in my Dropbox with this Seti Reschedulers link.

I think Jeff's is particularly nice since there are both Windows and Linux versions and the fact they are GUI's make them simple to use.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

That's why BOINC 7.4.44 was developed.

Just curisity it still has the 1000 WU limit or that was changed to 3000?

Are you asking about 7.4.44 or 7.8.3? 7.4.44 has the 3000 limit and 7.8.3 still has the 1000 limit.

i know this is kind of mixing threads a bit. but i was looking at wildcard's 13-GPU host. i was wondering if he'd hit the 1000 limit (he's on 7.9.3) since he has 13 GPUs (x100 per = 1300)

interestingly enough it shows over 3000 in progress. https://setiathome.berkeley.edu/results.php?hostid=8568434

how can this be?

i thought under normal circumstances you'd only get your [# of GPU]x100 + 100 for CPU, and even with recheduling you couldnt get over the BOINC limit (3000 on 7.4.44, and 1000 on the newer 7.8.3 and up versions). with some ghosts, sure he could get over the limit maybe, but he's over 2000 tasks over his limit. what do you think?

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

I would bet on ghosts or possibly leftovers if he converted a previous Windows machine to Linux and kept the host ID.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

He runs Boinc 7.9.3. Does anybody knows what is the WU limit on this build?

By Free-DC today's stats:

8568434	wildcardcorp.com 628,565
7475713	petri33 381,247

---

All builds are set to 1000, it's in the code.
All you have to do to find Ghosts is to go back far enough to find Unfinished tasks prior to finished tasks, here, https://setiathome.berkeley.edu/results.php?hostid=8568434&offset=16360
He has, State: All (19541), with Ghosts back at16020.

All BOINC versions past 7.0.2 have the 1000 task limit. Only the specially compiled TBar 7.4.44 has the 3000 task limit.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I have made all of the reschedulers available in my Dropbox with this Seti Reschedulers link.

Dear Keith, I was very curious about the reschedulers you made available (thank you), in particular Jeff's, that you cherish particularly.
But I seem not to be able to extract the .7z files (not only Jeff's) with any means I know of (such as the obvious Ark and others I tested on the occasion).

What am I doing wrong (or what is the "trick")?

Thank you!

Sleepy

Install a 7zip application, it is similar to WinZip.

I have made all of the reschedulers available in my Dropbox with this Seti Reschedulers link.

I'm getting "Too many requests", is the link banned due to traffic?

Same here in Canada on that link.

I'm hoping that the seti team has figured out the problem the system has been having and address it during Tuesday's down time.

Right now the system should be running well as there isn't heavy demand, and no noise bombs in the data, but still I see some bad signs.
The db isn't being purged. It is at 3.6 million right now and can get alot higher before crashing, so this could be a false alert, or an early warning sign.
(edit : false alarm, my list of valids is back to 24 hours - so db is being purged)

27se18ab splitting seems to have stopped or be stuck.

The good news is if the system can stay up, then we have enough datafiles available to get us through the weekend.

Just a warning when you use some reschedulers:

If you run the linux special cuda apps be aware, the builds not like to suspend a WU in the middle of the crunching process.

Sometimes things weird happening like crashing the WU process or even worst, send the WU to be crunched by the CPU and stop the GPU crunch until that process ended (a big loss in GPU processing time while wait).

If you look at the docs supplied with the builds they talk about to be care not to suspend the WU in the middle of the process.

From the README file:

6) The App may give Incorrect results on a restarted task. One way to avoid restarted tasks is to set the checkpoint higher than the task's estimated run-time, and also avoid suspending a task.

---

db_purge: Deletes result/workunit records when no longer needed (i.e. after the associated files have been deleted). Depending on server load, we usually wait 24 hours between the files have been removed before purging the corresponding results so people can still view these results online for a day after they've been processed/assimilated. This program keeps our BOINC database as small as possible so that it fits in RAM (and therefore operates much faster).

Since the Assimilator just went through a pile of files less than 24h ago, the purge numbers will be high.

And yea, I hope they sort things out with the dB. The outage last Sunday/Monday Eric mentioned to me

Database issue. Logical log backups were waiting on a keypress. It should be working now, but will take some time to build a work queue.

I don't know if that was on the Master or Science database. My thought is the latter. I don't know what happened yesterday, but ecpect it was the same.

And yea, I hope they sort things out with the dB. The outage last Sunday/Monday Eric mentioned to me

Database issue. Logical log backups were waiting on a keypress. It should be working now, but will take some time to build a work queue.

I don't know if that was on the Master or Science database. My thought is the latter. I don't know what happened yesterday, but expect it was the same.

I think we should all club together and buy Eric one of these:

Feely finger phone

The MobiLimb finger can crawl across the desk, waggle for attention when messages arrive and be used as an interface to control apps and games.

I have made all of the reschedulers available in my Dropbox with this Seti Reschedulers link.

I'm getting "Too many requests", is the link banned due to traffic?

That is the first time I've heard of this issue. I had to investigate what the limits for a free Dropbox account was. This is from the Help community answer.

Dropbox Basic (free) accounts:

The total amount of traffic that all of your links and file requests together can generate without getting banned is 20 GB per day.
The total number of downloads that all of your links together can generate is 100,000 downloads per day.

I find it hard to believe any downloads added up to 20GB or over 100,000 requests. None of the Rescheduler files is more than a meg is size.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Just a warning when you use some reschedulers:

If you run the linux special cuda apps be aware, the builds not like to suspend a WU in the middle of the crunching process.

Sometimes things weird happening like crashing the WU process or even worst, send the WU to be crunched by the CPU and stop the GPU crunch until that process ended (a big loss in GPU processing time while wait).

If you look at the docs supplied with the builds they talk about to be care not to suspend the WU in the middle of the process.

From the README file:

6) The App may give Incorrect results on a restarted task. One way to avoid restarted tasks is to set the checkpoint higher than the task's estimated run-time, and also avoid suspending a task.

No Rescheduler will move a task that is in the process of being crunched. So this warning is not valid.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I guess we will have to wait for the banning to end. I deleted the link to not generate any more download requests. Once the account allows downloads again, I can make a new link to a rescheduler file on a personal request if whoever is interested gives me a email address to share to.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)