Welcome to MilkyWay@home

Posts by Ged

1) Message boards : Number crunching : Server can't open database? (Message 68156)
Posted 13 Feb 2019 by Profile Ged
Post:
Thanks again Keith.

Ged
2) Message boards : Number crunching : Server can't open database? (Message 68146)
Posted 12 Feb 2019 by Profile Ged
Post:
Thanks Keith.

I get what you're suggesting but it would bother me that cc_config.xml is a global configuration item for cpu-bound projects; nvc-config.xml would have to be set to cover gpu-bound apps, too.

Also, I thought that <http_transfer_timeout> is to do with project file transfers to/from client/server - If it's taking longer than the value you specify (default is 300 seconds...) then 'Abort' the transfer. This, along with the <http_transfer_timeout_bps> configuration item, which allows you to specify a minimum/acceptable data transfer rate, allows for those using dial-up modem connections (nostalgia!!!) to not waste call time on an unacceptably slow connection, for example:

<http_transfer_timeout>90</http_transfer_timeout>
<http_transfer_timeout_bps>9600</http_transfer_timeout_bps>

Would tell the client to abort the file transfer if the effective connection speed was less than 9600 bits per second for 90 seconds.

I'm still of the mind that the Milkyway project team need to fix the fundamental issue at their end ;-)

Ged
3) Message boards : Number crunching : Server can't open database? (Message 68136)
Posted 11 Feb 2019 by Profile Ged
Post:
These DB outages are bad enough on the Milkyway project but they also impact other projects I run on my machines. When BOINC Manager issues an update request for Milkyway@Home, either to report completed work or because I asked for an update against the project, BOINC puts that request on a sequential stack. If other running projects cause an update of their status while the Milkyway request is being processed and Milkyway's DB is down then due to the extraordinarily long time it seems to take just to say "it's broken" those other project requests can't be serviced until Milkyway issues a reply.

So can Milkyway project admins please stop ignoring this problem and put some technical effort into operational efficiency improvements at the brief expense of the cascade of application development? I'm sure it will be worth the effort.

Ged
4) Message boards : Number crunching : Is MW just a GPU project now? (Message 54669)
Posted 5 Jun 2012 by Profile Ged
Post:
Read the News thread, it says power outage causing some computers to be down, specifically the work generation ones!


Thanks, Mikey - I'd asked my question a good while before Travis's news item about the power and consequential jump server (SSH acces et al) outages - I appreciate your response, nonetheless.

Ged
5) Message boards : Number crunching : Is MW just a GPU project now? (Message 54666)
Posted 5 Jun 2012 by Profile Ged
Post:
Vielen Dank, an alle Mitglieder der DSKAG Gemeinschaft.

Mit freundlichen Grüßen,

Ged

Many thanks to all members of the dskagcommunity.

With kind regards,

Ged
6) Message boards : Number crunching : Is MW just a GPU project now? (Message 54659)
Posted 4 Jun 2012 by Profile Ged
Post:
Hi Everyone,

I've been trying to get work units to crunch and notice that when there are many available, none seem to be for CPU-based crunching - Hence my question in the thread title...

Can anyone advise, please?

(I'm aware that Travis and others have been busy implementing and deploying for a new algorithm.)

Thanks in advance,

Ged




©2024 Astroinformatics Group