We have implemented new functionality in our workunit generator that will automatically will keep the number of unsent results in the database at a certain level (currently 500).
Yet boinc manager recieves this message still
18/10/2006 19:18:18|Docking@Home|
Message from server: No work sent
18/10/2006 19:18:18|Docking@Home|
Message from server: (there was work but it was committed to other platforms)
I suspect that unsent results consists of ones for each platform (windows, mac, linux and so on). How about separating these and set the level of unsent results for each of them, so that hosts can recieve workunits and crunch them all day long?
thanks for reading,
suguruhirahara
____________
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions.
This is due to a problem with homogeneous redundancy. We are working on a fix for the feeder to make this message go away. It has nothing to do with the workunit generator, but with the shared memory that has many results reserved for linux's and macs so that there is nothing left for windows. It also makes a difference if you have an intel or amd cpu. So there might be work for windows on amd, but not for windows on intel. We are currently reviewing all of these policies in the light of our recent findings.
Thanks
Andre
We have implemented new functionality in our workunit generator that will automatically will keep the number of unsent results in the database at a certain level (currently 500).
Yet boinc manager recieves this message still
18/10/2006 19:18:18|Docking@Home|
Message from server: No work sent
18/10/2006 19:18:18|Docking@Home|
Message from server: (there was work but it was committed to other platforms)
I suspect that unsent results consists of ones for each platform (windows, mac, linux and so on). How about separating these and set the level of unsent results for each of them, so that hosts can recieve workunits and crunch them all day long?
thanks for reading,
suguruhirahara
____________
D@H the greatest project in the world... a while from now!
Mit 18 Okt 2006 22:09:23 CEST|Docking@Home|Sending scheduler request to http://docking.utep.edu/docking_cgi/cgi
Mit 18 Okt 2006 22:09:23 CEST|Docking@Home|Reason: To fetch work
Mit 18 Okt 2006 22:09:23 CEST|Docking@Home|Requesting 8640 seconds of new work
Mit 18 Okt 2006 22:09:28 CEST|Docking@Home|Scheduler request succeeded
Mit 18 Okt 2006 22:09:28 CEST|Docking@Home|Message from server: No work sent
Mit 18 Okt 2006 22:09:28 CEST|Docking@Home|Message from server: (there was work but it was committed to other platforms)
Mit 18 Okt 2006 22:09:28 CEST|Docking@Home|No work from project
This is so since 0800UTC.
So if it's homogenous redundancy it's 500 Mac-WUs ;)
Hmmm, this is definitely weird. Will dive deeper into this...
AK
Nothing for Linux as well:
Mit 18 Okt 2006 22:09:23 CEST|Docking@Home|Sending scheduler request to http://docking.utep.edu/docking_cgi/cgi
Mit 18 Okt 2006 22:09:23 CEST|Docking@Home|Reason: To fetch work
Mit 18 Okt 2006 22:09:23 CEST|Docking@Home|Requesting 8640 seconds of new work
Mit 18 Okt 2006 22:09:28 CEST|Docking@Home|Scheduler request succeeded
Mit 18 Okt 2006 22:09:28 CEST|Docking@Home|Message from server: No work sent
Mit 18 Okt 2006 22:09:28 CEST|Docking@Home|Message from server: (there was work but it was committed to other platforms)
Mit 18 Okt 2006 22:09:28 CEST|Docking@Home|No work from project
This is so since 0800UTC.
So if it's homogenous redundancy it's 500 Mac-WUs ;)
____________
D@H the greatest project in the world... a while from now!
Don 19 Okt 2006 06:13:13 CEST|Docking@Home|Sending scheduler request to http://docking.utep.edu/docking_cgi/cgi
Don 19 Okt 2006 06:13:13 CEST|Docking@Home|Reason: To fetch work
Don 19 Okt 2006 06:13:13 CEST|Docking@Home|Requesting 8640 seconds of new work
Don 19 Okt 2006 06:13:18 CEST|Docking@Home|Scheduler request succeeded
Don 19 Okt 2006 06:13:18 CEST|Docking@Home|Message from server: No work sent
Don 19 Okt 2006 06:13:18 CEST|Docking@Home|Message from server: (there was work but it was committed to other platforms)
Don 19 Okt 2006 06:13:18 CEST|Docking@Home|No work from project
Yes. But that doesn't mean they will be added to the shared memory as well. When hosts request work they get it from the shared memory segment and if the shared memory segment has marked results as a windows, linux or mac result, the rest of the result from that workunit have to go to a windows, linux or mac as well: they are so to say reserved by that platform and other platforms won't get these. If all results have been reserved, the message you are seeing is being sent out.
Hope that makes it clearer. We'll make a FAQ entry on this as well, because there seem to be many questions on this.
Thanks!
Andre
[As of 19 Oct 2006 10:14:23 UTC] : Results ready to send 635
What will happen if it'll go under 500? Will other new unsent results be added to the database?
____________
D@H the greatest project in the world... a while from now!
We have increased the running time of our workunits slightly (added 1.5 hours on a 3 GHz P4). This will hopefully have as an effect that PCs will not come back to the server so often and request less results, thereby alleviating the HR reservation effect on the shared memory segment. In other words, you should not see the \'Work has been commited to other platforms\' so often anymore.
Does this mean that this issue has solved and the database is working without problem?
____________
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions.
No not yet, but hopefully it has alleviated the problem a bit and you won't see the famous message so much.
Andre
We have increased the running time of our workunits slightly (added 1.5 hours on a 3 GHz P4). This will hopefully have as an effect that PCs will not come back to the server so often and request less results, thereby alleviating the HR reservation effect on the shared memory segment. In other words, you should not see the 'Work has been commited to other platforms' so often anymore.
Does this mean that this issue has solved and the database is working without problem?
____________
D@H the greatest project in the world... a while from now!
No not yet, but hopefully it has alleviated the problem a bit and you won't see the famous message so much.
Andre
Understood.
Also,
[As of 20 Oct 2006 15:11:46 UTC] Results ready to send 500
It seems that generator is well adding unsent results to the database, keeping the same level.
EDIT:
but I fear that the increasing of running time would bring a mac / PIII (or Windows Vista) machine to have a disadvantage in that results returned by the host sometimes are invalidated. Some of the participants will be frustrated. This project is however yet in alpha-phase, though.
____________
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions.
EDIT:
but I fear that the increasing of running time would bring a mac / PIII (or Windows Vista) machine to have a disadvantage in that results returned by the host sometimes are invalidated. Some of the participants will be frustrated. This project is however yet in alpha-phase, though.
That's the next problem that will hopefully be solved soon, but we need the new Charmm release for this and unfortunately that still hasn't been released.
Andre
____________
D@H the greatest project in the world... a while from now!
My computer managed to grab 3 WUs while I was at work today, but I am already getting the dreaded 'Work has been commited to other platforms' message again.
My computer managed to grab 3 WUs while I was at work today, but I am already getting the dreaded 'Work has been commited to other platforms' message again.
That was because the shared memory segment issue hasn't been fixed yet. We'll sometimes see the message until it'll be solved.
____________
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions.