Of the 11 Einstein tasks now shown on my computer, one is an
All-Sky Gravitational; Wave Search on 031.07 (GW-opencl-ati-3)
The other Einstein tasks show completion times of 6 to 9 hours, which is a lot, but I can live with that. They frequently complete in less time than predicted.
However, the 031,07 task shows a completion time of 18days, 12:.59;08.
The previous one started out at about 18 days, but when I let it run for half a day, the completion time was changed to 33 days. That is not acceptable and I aborted it.
This computer:
Authentic AMD
AMD Ryzen 7 5700G with Radeon Graphics [Family 25 Model 80 Stepping 0]
(16 processors)
AMD AMD Radeon(TM) Graphics (6227MB)
Microsoft Windows 11
Core x64 Edition, (10.00.22621.00)
In addition to Einstein, it is also running Asteroids, Milky Way, Universe, WCG, Rosetta.
I will probably abort the current 031,07 task too, unless you can give me a compelling reason not to do that.
Of the 11 Einstein tasks now shown on my computer, one is an
All-Sky Gravitational; Wave Search on 031.07 (GW-opencl-ati-3)
The other Einstein tasks show completion times of 6 to 9 hours, which is a lot, but I can live with that. They frequently complete in less time than predicted.
However, the 031,07 task shows a completion time of 18days, 12:.59;08.
The previous one started out at about 18 days, but when I let it run for half a day, the completion time was changed to 33 days. That is not acceptable and I aborted it.
This computer:
Authentic AMD
AMD Ryzen 7 5700G with Radeon Graphics [Family 25 Model 80 Stepping 0]
(16 processors)
AMD AMD Radeon(TM) Graphics (6227MB)
Microsoft Windows 11
Core x64 Edition, (10.00.22621.00)
In addition to Einstein, it is also running Asteroids, Milky Way, Universe, WCG, Rosetta.
I will probably abort the current 031,07 task too, unless you can give me a compelling reason not to do that.
Steven Gaber
Oldsmar, FL
If you abort it someone else will just get it and run in, it's not really a big deal if you abort it.
Of the 11 Einstein tasks now shown on my computer, one is an
All-Sky Gravitational; Wave Search on 031.07 (GW-opencl-ati-3)
The other Einstein tasks show completion times of 6 to 9 hours, which is a lot, but I can live with that. They frequently complete in less time than predicted.
However, the 031,07 task shows a completion time of 18days, 12:.59;08.
The previous one started out at about 18 days, but when I let it run for half a day, the completion time was changed to 33 days. That is not acceptable and I aborted it.
This computer:
Authentic AMD
AMD Ryzen 7 5700G with Radeon Graphics [Family 25 Model 80 Stepping 0]
(16 processors)
AMD AMD Radeon(TM) Graphics (6227MB)
Microsoft Windows 11
Core x64 Edition, (10.00.22621.00)
In addition to Einstein, it is also running Asteroids, Milky Way, Universe, WCG, Rosetta.
I will probably abort the current 031,07 task too, unless you can give me a compelling reason not to do that.
Steven Gaber
Oldsmar, FL
You have an AMD Radeon GPU with 6GB memory, and you also have just 16GB of system memory. Yet you are running six projects. It is my guess that you are running out of memory when trying to do the file in question. To narrow it down, try placing the other projects in Suspend mode in your BOINC Manager and then let this one file run some more. If it completes, my hunch is right. Then you need to make some changes to your computer settings in Preferences.
Also, are you using the web for all project preferences, or are you using your local computer for preferences. If you are using the web, then what you set for your last project becomes the preferences for all projects. Things like:
Suspend computing when your computer is busy running other programs.
Keep some CPUs free for other applications. Example: 75% means use 6 cores on an 8-core CPU.
Suspend/resume computing every few seconds to reduce CPU temperature and energy usage. Example: 75% means compute for 3 seconds, wait for 1 second, and repeat.
Limit the memory used by BOINC when you're using the computer.
Limit the memory used by BOINC when you're not using the computer.
These settings are important, if you have them set to a medium level so you can still use your computer you are very likely running out of memory. Either live with your problem file(s) or pare down some of your projects, or upgrade your system memory.
The server that collects the results of this search is filling up faster than I can get the data off it. I'll suspend sending new GW tasks for a couple of days.
The server that collects the results of this search is filling up faster than I can get the data off it. I'll suspend sending new GW tasks for a couple of days.
If I'd seen this about an hour or two ago, it would have saved me a *lot* of angst.
I was just trying to start a machine that was properly configured but had run out of work because it had insufficient disk space. After doubling the partition size and making sure BOINC was allowed to use it all, I kept getting a very simple 'not sending any work' type of message with no other type of explanation as to why.
It should be very useful to others wondering why, if the message could be supplemented by something like 'work generation temporarily suspended server-side' so that people don't spend a lot of wasted effort trying to work out how they might have stuffed up their local configuration. Lots of people probably don't read the boards regularly but some sort of high visibility announcement might help.
Due to the relatively short deadline for O3AS, there will be lots of people with small cache sizes quickly running out and wondering why they can't get more. If work is out for "a couple of days", all of mine will run out. That will be quite painful for me because I've developed a 'task staggering system' that needs quite a bit of user intervention to get it properly started. The performance gains make it very worthwhile so I guess I'll just have to suck it up.
It probably won't be suitable for all users, but to manage these types of temporary outages, I keep my Project Preferences set to allow non-preferred apps. At the moment, O3AS (my preferred app) is being replaced with BRP7 MeerKAT work.
Ideas are not fixed, nor should they be; we live in model-dependent reality.
In contrast to Asteroids@home this project has plenty of tasks available, just currently not for that particular application. If you click on the "Last time contacted server" time of your host you can take a look at the relevant part of the scheduler log, which tells you more than the one-line messages to the client could. E.g. it should tell you which applications it tried to find work for.
Edit: actually I think in case of "no work sent" the link to the longs should also be transmitted as a message to the client.
The server that collects the results of this search is filling up faster than I can get the data off it. I'll suspend sending new GW tasks for a couple of days.
Of the 11 Einstein tasks now
)
Of the 11 Einstein tasks now shown on my computer, one is an
All-Sky Gravitational; Wave Search on 031.07 (GW-opencl-ati-3)
The other Einstein tasks show completion times of 6 to 9 hours, which is a lot, but I can live with that. They frequently complete in less time than predicted.
However, the 031,07 task shows a completion time of 18days, 12:.59;08.
The previous one started out at about 18 days, but when I let it run for half a day, the completion time was changed to 33 days. That is not acceptable and I aborted it.
This computer:
AMD Ryzen 7 5700G with Radeon Graphics [Family 25 Model 80 Stepping 0]
(16 processors)
Core x64 Edition, (10.00.22621.00)
In addition to Einstein, it is also running Asteroids, Milky Way, Universe, WCG, Rosetta.
I will probably abort the current 031,07 task too, unless you can give me a compelling reason not to do that.
Steven Gaber
Oldsmar, FL
S. Gaber
Steven Gaber wrote: Of the
)
If you abort it someone else will just get it and run in, it's not really a big deal if you abort it.
Steven Gaber wrote: Of the
)
You have an AMD Radeon GPU with 6GB memory, and you also have just 16GB of system memory. Yet you are running six projects. It is my guess that you are running out of memory when trying to do the file in question. To narrow it down, try placing the other projects in Suspend mode in your BOINC Manager and then let this one file run some more. If it completes, my hunch is right. Then you need to make some changes to your computer settings in Preferences.
Also, are you using the web for all project preferences, or are you using your local computer for preferences. If you are using the web, then what you set for your last project becomes the preferences for all projects. Things like:
These settings are important, if you have them set to a medium level so you can still use your computer you are very likely running out of memory. Either live with your problem file(s) or pare down some of your projects, or upgrade your system memory.
Proud member of the Old Farts Association
the (or one of?) O3AS
)
the (or one of?) O3AS validator seems to be lagging. validation queue climbing 10k+ now. might be hung up or need some kind of kick.
_________________________________________________________________________
The server that collects the
)
The server that collects the results of this search is filling up faster than I can get the data off it. I'll suspend sending new GW tasks for a couple of days.
BM
Bernd Machenschalk wrote:The
)
If I'd seen this about an hour or two ago, it would have saved me a *lot* of angst.
I was just trying to start a machine that was properly configured but had run out of work because it had insufficient disk space. After doubling the partition size and making sure BOINC was allowed to use it all, I kept getting a very simple 'not sending any work' type of message with no other type of explanation as to why.
It should be very useful to others wondering why, if the message could be supplemented by something like 'work generation temporarily suspended server-side' so that people don't spend a lot of wasted effort trying to work out how they might have stuffed up their local configuration. Lots of people probably don't read the boards regularly but some sort of high visibility announcement might help.
Due to the relatively short deadline for O3AS, there will be lots of people with small cache sizes quickly running out and wondering why they can't get more. If work is out for "a couple of days", all of mine will run out. That will be quite painful for me because I've developed a 'task staggering system' that needs quite a bit of user intervention to get it properly started. The performance gains make it very worthwhile so I guess I'll just have to suck it up.
Cheers,
Gary.
It probably won't be suitable
)
It probably won't be suitable for all users, but to manage these types of temporary outages, I keep my Project Preferences set to allow non-preferred apps. At the moment, O3AS (my preferred app) is being replaced with BRP7 MeerKAT work.
Ideas are not fixed, nor should they be; we live in model-dependent reality.
It would be nice if the
)
It would be nice if the server would tell a bit more when requesting new work.
e.g. this is useful:
Do 28 Mär 2024 22:09:14 CET | Asteroids@home | Project has no tasks available
This is the Einstein way:
Do 28 Mär 2024 22:09:52 CET | Einstein@Home | No work sent
In contrast to Asteroids@home
)
In contrast to Asteroids@home this project has plenty of tasks available, just currently not for that particular application. If you click on the "Last time contacted server" time of your host you can take a look at the relevant part of the scheduler log, which tells you more than the one-line messages to the client could. E.g. it should tell you which applications it tried to find work for.
Edit: actually I think in case of "no work sent" the link to the longs should also be transmitted as a message to the client.
BM
Bernd Machenschalk
)
ready to turn it back on before the weekend? :)
_________________________________________________________________________