Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 7
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1007 times and has 6 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
confused Projects

Just curious, under the device settings all of mine are on customs times. If one device (lets say it has the name Dragon) has not finished crunching the data and there is another device (lets have the name Cloud) scheduled to start, what happens to Dragon? Does Dragon resume the data that it had been doing previously or start a new one when his time is back on?
[Jan 19, 2006 5:40:34 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Projects

Devices don't share data. Your computers will almost certainly be working on different work units, and if (by coincidence) they are working on the same work unit, each computer will have its own copy, and perform the simulation in its entirety.

Your device will only discard the work unit it has been working on and get another if the current work unit is too old to be useful. This is a long period, and isn't normally relevant.
[Jan 19, 2006 6:25:30 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Projects

And if theyre on the same computer? And how do they change over? N00bie question I guess
----------------------------------------
[Edit 1 times, last edit by Former Member at Jan 19, 2006 7:12:45 AM]
[Jan 19, 2006 7:09:26 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Projects

My understanding is multiple copies of the UD agent on the same computer don't play nicely together. Is this what you are trying to do? Why?
[Jan 19, 2006 7:39:49 AM]   Link   Report threatening or abusive post: please login first  Go to top 
RT
Master Cruncher
USA - Texas - DFW
Joined: Dec 22, 2004
Post Count: 2636
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Projects

I think we need more information in order to be of help. First of all, are we talking about the BOINC agent or the UD agent? Secondly, are these "devices" on the same or different machines?
----------------------------------------
One of your friends in Texas cowboy
RT Website Hosting

[Jan 19, 2006 1:36:41 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Projects

Were talking about the UD agent and they are on the same computer.
[Jan 20, 2006 12:56:43 AM]   Link   Report threatening or abusive post: please login first  Go to top 
retsof
Former Community Advisor
USA
Joined: Jul 31, 2005
Post Count: 6824
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Projects

Just curious, under the device settings all of mine are on customs times. If one device (lets say it has the name Dragon) has not finished crunching the data and there is another device (lets have the name Cloud) scheduled to start, what happens to Dragon? Does Dragon resume the data that it had been doing previously or start a new one when his time is back on?
I would guess that Dragon resumes at the last checkpoint when it starts again. It's just like turning the computer off/on.

I found that messing with the times was very unoptimal, and I couldn't set different times for the weekend. Unfortunately, you also have to send things in in the same time window. You will lose the unfinished time between checkpoints each time that you start a different device in a different time window.

I find it easier to leave everything at 24/7 and manage multiple devices with UDMonitor. Each device runs to completion, and UDMonitor then automatically switches to the next oldest one. I have two AMD64 computers that are completing 5-6 workunits per day each. Fooling with the times to manage that just doesn't make sense. I also have 30 slots(devices) on each computer, enough work to last 5-7 days in case the server is unavailable or something.

It is also possible to use different profiles for each device. You have discovered that because each of yours has a different time window. I have three profiles at the moment: One for both projects, one for HPF only and one for FA@H only. The AMDs are bashing away at FA@H while a slow Pentium III works only on HPF.

Without looking at the detail screen, you can check the color of the UDMonitor flask icon.

UDMonitor changes the color of the flask icon to denote checkpoint time:
blue, recent checkpoint saved not too long ago
yellow, has been awhile
red, has been a long time since the last checkpoint (It would be better to wait a little while before looking for other results or turning off the computer. The next checkpoint should be along shortly.)

You can look at the log to see how long it has been between checkpoints. Depending on the workunit, I see anything between 4 minutes and 25 minutes for FA@H. My current workunit is taking a checkpoint about every 6 minutes and 30 seconds.

BOINC handles multiple workunits, and UDMonitor is not needed in that case.
----------------------------------------
SUPPORT ADVISOR
Work+GPU i7 8700 12threads
School i7 4770 8threads
Default+GPU Ryzen 7 3700X 16threads
Ryzen 7 3800X 16 threads
Ryzen 9 3900X 24threads
Home i7 3540M 4threads50%
----------------------------------------
[Edit 4 times, last edit by retsof at Jan 20, 2006 2:03:35 AM]
[Jan 20, 2006 1:48:37 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread