don't even know if I can exchange them for quatloos
just know they stopped coming

---

don't even know if I can exchange them for quatloos
just know they stopped coming

At the current it will take the validators 7 days to give you your credit - just hang in there.

---

.


A person who makes no mistakes, creates nothing.

At the current it will take the validators 7 days to give you your credit - just hang in there.

Or longer. I have some returned results that have been pending for over 8 days.

It seems like the newest PCs out there became more powerful than BOINC can handle :-)

---

It seems like the newest PCs out there became more powerful than BOINC can handle :-)

I do agree about that. "Earlier…" I've always had around 10 WUs waiting - lately this number increased for every week. I have now between 40 - 50 waiting for validation. Obviously BOINC can't manage the load...

Happy crunching

---

Happy crunching

Since you people do not seem to read the forums, as this is discussed over and over, I will try to quickly explain.

The validators are behind. They are behind because the file deleters haven't been doing their proper job, and the directories are overcrowded. When there are too many files in directories, it slows the lookups down.

Berkeley is working on this situation, but has not found the perfect solution, yet. So the validators get more and more behind. If you look at the server page the waiting for validation is over 800K.

Good luck in all your future endevors.

---

My movie https://vimeo.com/manage/videos/502242

and just to add to Pooh's comments... this is not a case of BOINC not being able to cope at all. BOINC is the framework, it's SETI thats having problems coping (at the moment). This is a perfect example of why BOINC was created, connect to another project and you can happily continue crunching for other worthy causes in the event of any problems/downtime. :)

---

Raithmir's SPARC64/UltraSPARC Linux Builds
http://www.kulthea.net/boinc/

and just to add to Pooh's comments... this is not a case of BOINC not being able to cope at all. BOINC is the framework, it's SETI thats having problems coping (at the moment). This is a perfect example of why BOINC was created, connect to another project and you can happily continue crunching for other worthy causes in the event of any problems/downtime. :)

I think you're right.
So I will stop working for seti - in hope that the project will fix the current problems - an switch to einstein and predictor, some projects I spend less time normally.

Stefan

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=710c1e51b47b1aa3c4b24b13251cb271"> <img src="http://www.boincstats.com/stats/teambanner.php?teamname=armageddon">

Just becuase it is taking time for credit to be passed back by SETI it does not mean that it is less worthwhile still crunching for them. I will carry on and wait patiently for my credits.

---

Just becuase it is taking time for credit to be passed back by SETI it does not mean that it is less worthwhile still crunching for them. I will carry on and wait patiently for my credits.

I'm not sure what will happen next. Could be they tell us, that some credits have to be canceled or so - to solve some problems.
Could be all units will be credited some day - who knows.

In my opinion it's a good moment to do more work for other projects.
If more people will do so - the seti-backlog of waiting results should be caught up faster (or it doesn't grows as fast as in the moment).

Greetings
Stefan

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=710c1e51b47b1aa3c4b24b13251cb271"> <img src="http://www.boincstats.com/stats/teambanner.php?teamname=armageddon">

The will get credited eventually. They are looking at several things to fix this, including new file systems that allow for larger directories better.

My biggest suggestion would be a few hour outage, where they just run the deleter at full force for a few hours, to get the old results under control, then a few hours of just validating to get those caught up, then deleter again to clear, then bring the system up with directory sizes a lot less problematic.

If you think about how many files have to sit out there. Right now 800K * 3.5 (just averaging) for validation, then 500K * 4 for sending, and the users do not know how many are waiting for assimilation, deleting, etc. There are millions of files sitting out there.

Hope this helps those who are actually wondering.

I crunch for several projects, and keep Seti going, cause it's a worthy cause.

---

My movie https://vimeo.com/manage/videos/502242

Pooh, you're correct!
Some of us don't read all forums here in detail; it would take too much time to keep your self updated on all single subjects. I browse them trough in between but my experience is that it's to much wining... so I get kind of tired to read all about minor and major problems.

As noticed in another answer in this thread I will correct my careless statement saying that BOINC is not coping with the load. Of course this has nothing to do with BOINC it self it is all about the infrastructure dealing with received WU's Sorry about that!

I participate in several projects as well and am not very concerned if I have WU's for SETI or not - there will always be something to crunch from other projects. However, I do prefer to crunch for SETI since that’s what caught me in first place.

As long as we can download WU’s and upload the same I’m happy. Credit will come sooner or later.

Happy crunching!

---

Happy crunching

I agree with several of you. One of my computers is strictly doing Seti WU's, got about 40+ waiting now, but on this machine I'm on, I at one point had about the same amount of wu's waiting, then all of a sudden got a huge rush of credits. I don't know how many days it took. Didn't pay attention to that, but as Pooh has said, maybe that would work temperarily. But a good hard core fix would be best, so that they don't have to keep doing outages, and keep doing what they are doing.

I could care less when my credits come in. This computer happily crunches Einstein too. And unless UCB really wants everyone to stop crunching Seti WU's to help with the backlog, I'm going to continue to happily crunch them.

Happy Crunching All!

Jeremy

---

I'm a bit worried about the Seti-boinc's current state. The servers can't keep up because of the file amounts and there is more coming all the time. Which means the servers are getting more behind all the time. Of course this is a good stress-test for Seti-boinc :) .

But I'm hoping the folks at Berkeley can solve the problems and no calculated data is lost.

---

Do the people working on this know that for most file systems deleting files from a directory does not make the directory smaller? It just marks those entries deleted. On a later lookup that entry is scanned and then dropped from the result list because it's marked deleted.
Most file systems need something like the "-D" option to fsck to actually remove the deleted entries from the directory. Too bad fsck can only happen on an unmounted fs.
I'd say that the things that should be considered are new file systems that operate orders faster at the leaf level and possibly do not exhibit the behaviour above, and making a tree of directories. Someone claimed that a tree was not a good solution as it was somehow inelegant. It sure is a lot more elegant than doing nothing. The hashing method can be incredibly simple/fast, and a three level tree could reduce the load by three orders of magnitude. Seems pretty elegant to get three orders of magnitude impovement in speed for the extra checks in a linear space of 10 items.

---