LHC@home

lucky you
all i get is 'no work from project'

Hey, all my pending downloads are now "ready to run". It took a couple days, but good job folks.

tony

Oh, I said nothing about getting new work. LOL These were "pending downloads" from days ago. Glad I didn't reset or anything like that.

tony

In case you are interested, this is what was going on while you had those pending downloads. If you are not interested then please skip the rest of this posting.

Different servers allocate work and distribute the files. In the case of LHC this is done be different software running on the same machine, in the case of projects with a larger throughput the separate software can sit on separate machines.

When you ask for work, the database machine tells your client which WU it has been allocated, and tells it which files it needs to have before it can run. You are now in pending download status. Your client then goes to the file server and asks for the files. While this is happening you are in status "Downloading". If anything goes wrong with that (network or the project servers) you drop back to "pending download".

Once all files are downloaded you are "Ready to Run", followed by "running", followed by "ready to upload", "uploading" (returning results to the fileserver), "ready to report". Eventually, once you are ready to report, your client will tell the database server you have done with that WU.

Most likely if you were stuck pending download for a long time, there was a problem on the file server (given that all this software is newly installed), or that the fileserver is overloaded (which often happens on this project just after new work comes available -- the databse can allocae it faster than the file server can deliver the files).

hope some people find this info enlightening
R~~

---

by the way I did not use the usual BOINC terms for the servers I mentioned in my recent post, and it is now too late to edit, just :(

so if you are reading more techie stuff on BOINC you may wish to know that:

- what I called the database server is more correctly called the scheduler;

- what I called the fileserver is more correctly called the upload/download server.

apols. R~~

hope some people find this info enlightening
R~~

I suppose you could sum all that up as:


Bottlenecks happen

---

sQuonk
Plague of Mice
Intel Core i3-9100 CPU@3.60 GHz, but it's doing its bit just the same.

;)