Gridview, in BOINC 5.10 and upwards, allows column sorting.

Yes, but only alphabetically, not "logically" ("Running on top...)

Gruß,
Gundolf

Trac, needs separate registration. Make a new ticket.

All I see there is a wiki, with information about the program and help files, I can't find any 'feature suggestion list', 'wishlist', or 'ideas' or anything similar to this thread, it may be there but I can't find it at all.

2: An option to say 'If a work unit is within x minutes (or above 99%) of finishing, continue on it' then give it like x*1.5 minutes before it moves to the next unit (so if it were looping or anything?)

Usually, BOINC runs to the next checkpoint, if the application checkpoints.
The problem is... BOINC cannot know how long the last 1% will take. On some projects it takes minutes, on others it takes days. Example given, the latest Orbit tasks take over 12 hours to do the last 0.050% on most systems. [/quote]

BOINC manager at least has the 'To Completion' time, so my thought was:
keepRunning = 5 minutes (a value set in the settings)
x = 'To Completion' time of current running work unit
if (x < keepRunning)
{
//Continue on this process for another (x*1.5) minutes
wait (x*1.5)
//if not completed by now go to another application
}
else
{
switch between applications normally
}

BOINC manager in the first tab of Preferences has the 'Switch between applications between every [] minutes'
So the above psudo-code would go where that triggers

And the reason for this is my philosophical beliefs on unloading/loading the application's memory when it only has a couple minutes to finish then uploading the data to the server could be done in the background of a different application.

I believe the waiting 150% of the 'to completion time' would work well even on projects that can produce work units that the time to finish the work unit can vary greatly, because even if some WUs would take 2 hours, others 10 hours, if this computer has gotten 10 2 hour ones (so the average it bases the completion time is 2 hours) then gets a 10 hour WU, and two hours into it the algorithm gives out 4 minutes left, my idea would give this application only 6 more minutes then switch normally, then the next time it came around it would probably give 6 or so minutes again, if it switches every hour, it would have given this application priority for almost an extra hour (10 switch times 6 minutes extra each time) which then the resource share will balance out and not run this for some hour in the future.

Gridview, in BOINC 5.10 and upwards, allows column sorting.

Yes as Gundolf Jahn said, I'm saying a logical sort.

(there is a chance i'm wrong about this, because i noticed it last night but no longer have two work units with the situation explained here)
I thought i'd mention, related to that, if you sort by "Report deadline"::
"8/15/08 1:23:53 PM" will be considered less than "8/15/08 2:33:53 AM"
So it didn't seem to consider AM vs PM, but only the date and 12hour time numbers

Trac, needs separate registration. Make a new ticket.

All I see there is a wiki, with information about the program and help files, I can't find any 'feature suggestion list', 'wishlist', or 'ideas' or anything similar to this thread, it may be there but I can't find it at all.

Look in the Menu bar. There's an option to see existing tickets (view tickets), you'll need to adjust your filters. Or try this one.

When making a ticket (new ticket), you need to change the type to enhancement.
If you want to receive emails on it, add the nickname you chose when you registered to the CC option. Do know that nicknames are best made of a single name, no spaces.

Or register to the BOINC Development email list and post it there. Either way is a somewhat more direct way to the eyes and ears of the developers than these forums are.

---

Gridview, in BOINC 5.10 and upwards, allows column sorting.

Yes, but only alphabetically, not "logically" ("Running on top...)

Gruß,
Gundolf

I've reopened [trac]#85[/trac] for this one.

---

Gridview, in BOINC 5.10 and upwards, allows column sorting.

Yes, but only alphabetically, not "logically" ("Running on top...)

Gruß,
Gundolf

I've reopened [trac]#85[/trac] for this one.

It's been added to the latest code, so perhaps that it is added to the client that's going to be released on Monday. Else you'll have to wait for BOINC 6.4 to see it.

---

Gridview, in BOINC 5.10 and upwards, allows column sorting.

Yes, but only alphabetically, not "logically" ("Running on top...)

Gruß,
Gundolf

I've reopened [trac]#85[/trac] for this one.

It's been added to the latest code, so perhaps that it is added to the client that's going to be released on Monday. Else you'll have to wait for BOINC 6.4 to see it.

What was in that new code? Just had a query at SETI, pointing out that sorting on the 'deadline' column uses a text sort, and if the user's regional settings have a single-digit hour format (h:mm:ss tt), then 9:59:59 doesn't sort next to 10:00:00. It works OK if you use hh:mm:ss, so that 09:59:59 comes before 10:00:00

Surely on type-numeric data columns (including date/time), the sorting should be done on the underlying numeric data, and then the formatting applied to the result? This appears to be "format as text first, then sort the text strings": not appropriate.

NB I have checked that the sorting behaviour is as described in BOINC Manager v6.2.18

I saw that guy's post. BOINC sorts on date before time. So in decreasing sorting a deadline of 11-11-08 12:56am will come after a deadline of 11-11-08 09.00am

Anyway, as far as I can follow, that code was available since 6.2.15 (or 6.3.6, depends on how you read the code ;-)).

---

I saw that guy's post. BOINC sorts on date before time. So in decreasing sorting a deadline of 11-11-08 12:56am will come after a deadline of 11-11-08 09.00am

Anyway, as far as I can follow, that code was available since 6.2.15 (or 6.3.6, depends on how you read the code ;-)).

Holy smoke, you're right. But it still seems to get confused by AM and PM:

is that one of yours? I ask as I thought you were still using 5.10.13 and swearing at the rest. ;-)

---

Just tested it on my system, I can't reproduce that with my 6.2.18, but that may be because I don't have that much work for all the same date. Could someone else with a larger cache and 6.2.18 please check?

(Go to Change country code, adjust, time, change time settings to hh:mm:ss tt and do set the AM and PM options. BOINC should pick it up automatically).

---

is that one of yours? I ask as I thought you were still using 5.10.13 and swearing at the rest. ;-)

I am - but I need to keep one sacrificial host so I know exactly what I'm swearing at, LOL.

That's the host which was running v6.2.14 until this happened yesterday.

is that one of yours? I ask as I thought you were still using 5.10.13 and swearing at the rest. ;-)

I am - but I need to keep one sacrificial host so I know exactly what I'm swearing at, LOL.

I do have a bit of good memory. It's Brian then that runs archaic 5.8.16

Knowing I had forgotten something, I just now answered to your other post. can't keep up with everything, sorry.

---

Just tested it on my system, I can't reproduce that with my 6.2.18, but that may be because I don't have that much work for all the same date. Could someone else with a larger cache and 6.2.18 please check?

(Go to Change country code, adjust, time, change time settings to hh:mm:ss tt and do set the AM and PM options. BOINC should pick it up automatically).

Probably fairest to exit and reload BOINC Manager after editing regional controls - give it a chance to fully acclimatise to the new settings. We're testing steady state, not transitions.

Won't be any problem to testers with daemon/service installs - crunching can continue through Manager testing.

A similar wish as Eibwen did:

If the remaining time (not percentage) of a WU is lower than x, this WU should be calculated first (in some applications it´s called "endgame mode").

x could be the same time as selected in the BOINC Manager at Advanced/Preferences/Processor usage/"switch between applications each x Minutes".

So it will be good, if there were a checkbox beneath this option.

The reason is that in contrast to my home-PC, which is running for 24/7, I´ve got some remote PCs at my family, where the Computers are not used regularly.

So it can happen, that there are some WUs with a remaining time of only some minutes, and BOINC "thinks" it´s okay, because the deadline of these WUs is some days later, and calculates for other projects.

Then the PC is turned off (at the weekend for example), and isn´t used for some days, so the deadline is reached and the almost-finished-WUs are worthless.

regards,
Alex

Edit:
An easier way:
There should be a way to disable the application-switching by setting the "switch-time" to zero.

An easier way:
There should be a way to disable the application-switching by setting the "switch-time" to zero.

You can achieve this by setting the "Switch between applications every ..." time to some large number, at least larger than the longest-lasting WU.

Peter

You can achieve this by setting the "Switch between applications every ..." time to some large number, at least larger than the longest-lasting WU.

Peter

Good idea, thanks!
Now I did so.

Alex

My wishes:

1. When BOINC is restarted (for any reason, PC restart, service stopped and then started) allow the ability to restart the tasks that were running before the stop, instead of picking a new task(s) to start running.

2. The ability to control the CPU usage while in use and when idle separately. I have a PC with 8 cores, I normally don't need all 8 and when I do I will stop BOINC. At the moment I can only dedicate X cores 100% of the time or it impacts my regular usage. Once I go home for the night (or a weekend) I want BOINC to take over the PC and use as much as it wants. The only options are RUN WHEN IDLE or RUN ALLWAYS ... I want both! (I know, just because I want it doesn't mean I'll get it)

Thanks.
Bill

---

Stupidity is billable... if you're going to be an idiot you're eventually going to have to pay for it. - Bill Miller

1. When BOINC is restarted (...) allow the ability to restart the tasks that were running before the stop, instead of picking a new task(s) to start running.

I do not give 1) a chance...

2. The ability to control the CPU usage while in use and when idle separately. [...] The only options are RUN WHEN IDLE or RUN ALLWAYS ... I want both! (I know, just because I want it doesn't mean I'll get it)

But fortunately you're not the only one...

I believe this is already worth a trac enhancement request ticket (I've recycled a very good matching Kathryn's [trac]#41[/trac], thanks for pointing it out, Sekerob).

Peter

My wish:
control over local temporary files.
Either let the BOINC manager clean up local temporary files automatically (after a configurable number of days), or provide a button to remove them manually.

BOINC already cleans up temporarily used files. These are in the slots directories which will be cleaned up as soon as the task is done.

If you mean that there's models left over in the CPDN directory (for instance), that's a thing that the project can take care of by deleting old files every so often (Einstein uses this method).

---