Both (application and server code) will not be used beyond the current S6CasA run, which is why I doubt that we'll spend any more work on either issue.
BM
Does that mean there will be no more S6CasA GPU work after this run?
There will be no more S6CasA work after the S6CasA run ended.
The current S6CasA OpenCL application code is pretty much limited to S6CasA (and btw. is bit for bit identical for ATI and NVidia). The author, Christophe Choquet, is already involved in the development of a successor for the next Gravitational Wave search on Einstein@Home.
I have also noticed one oddity here.
When I first enable to get new tasks on a machine (GW GPU enabled), the request takes too long and after a while, I get a HTTP server error.
Then the next request seems to work, though the WUs come as "lost". This happened on 2 different machines now, so it's not just a coincidence.
Quote:
Sending scheduler request: To fetch work.
Requesting new tasks for CPU and ATI Scheduler request failed: HTTP internal server error
Sending scheduler request: To fetch work.
Requesting new tasks for CPU and ATI
Scheduler request completed: got 12 new tasks Resent lost task h1_0999.35_S6Directed__S6CasAf40a_999.75Hz_289_3
I do have the same problem on my main rig.
Essentially this is because of the scheduler running too long, which is ultimately because of too many tasks being done by "Beta" versions.
I'm not sure that there is much headspace left in terms of efficiency of the implementation of the scheduler nor something we can easily do on the database server at the timescale of a few days.
However as you ultimately get the requested tasks I don't think this is a critical problem.
I suspect and hope that with a configuration change I made yesterday the load on the DB will get better in the next few days, and so should this problem.
Not sure if that's related, but I have noticed the number of my pending GW results has dropped significantly - from >1000 to 280. So that could be a good sign ;)
RE: Both (application and
)
Does that mean there will be no more S6CasA GPU work after this run?
-----
There will be no more S6CasA
)
There will be no more S6CasA work after the S6CasA run ended.
The current S6CasA OpenCL application code is pretty much limited to S6CasA (and btw. is bit for bit identical for ATI and NVidia). The author, Christophe Choquet, is already involved in the development of a successor for the next Gravitational Wave search on Einstein@Home.
BM
BM
RE: RE: I have also
)
Essentially this is because of the scheduler running too long, which is ultimately because of too many tasks being done by "Beta" versions.
I'm not sure that there is much headspace left in terms of efficiency of the implementation of the scheduler nor something we can easily do on the database server at the timescale of a few days.
However as you ultimately get the requested tasks I don't think this is a critical problem.
BM
BM
RE: However as you
)
Sure, no big issue ;-)
-----
I suspect and hope that with
)
I suspect and hope that with a configuration change I made yesterday the load on the DB will get better in the next few days, and so should this problem.
BM
BM
Not sure if that's related,
)
Not sure if that's related, but I have noticed the number of my pending GW results has dropped significantly - from >1000 to 280. So that could be a good sign ;)
-----