BT 0.28

Started by Corsair, November 14, 2009, 11:59:56 AM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Corsair

Hi all,  :D

very good improvements in this version, the history one I think is essential but should start the line with the ending of calculation time, on that way there is a very good reference if any computer has been idle for a while (a problem, or empty warehouse, etc.)

the sorting in the project windows now works as desired. :)
Roses don't bloom on the sailor's grave

Corsair.

fred

Quote from: Corsair on November 14, 2009, 11:59:56 AM
Hi all,  :D

very good improvements in this version, the history one I think is essential but should start the line with the ending of calculation time, on that way there is a very good reference if any computer has been idle for a while (a problem, or empty warehouse, etc.)

the sorting in the project windows now works as desired. :)
It starts with upload, and that's when a task completes.

Corsair

Quote from: fred on November 14, 2009, 12:02:02 PM
Quote from: Corsair on November 14, 2009, 11:59:56 AM
Hi all,  :D

the history one I think is essential but should start the line with the ending of calculation time, on that way there is a very good reference if any computer has been idle for a while (a problem, or empty warehouse, etc.)

It starts with upload, and that's when a task completes.

WU ready to report and no time stamp until reported.

still the sorting preferences in Tasks windows is not saved, e.g. if I select only 2 sorting
columns after restarting the program in tasks the 3rd column appear again.
Roses don't bloom on the sailor's grave

Corsair.

fred

Quote from: Corsair on November 14, 2009, 02:55:57 PM
Quote from: fred on November 14, 2009, 12:02:02 PM
Quote from: Corsair on November 14, 2009, 11:59:56 AM
Hi all,  :D

the history one I think is essential but should start the line with the ending of calculation time, on that way there is a very good reference if any computer has been idle for a while (a problem, or empty warehouse, etc.)

It starts with upload, and that's when a task completes.

WU ready to report and no time stamp until reported.

still the sorting preferences in Tasks windows is not saved, e.g. if I select only 2 sorting
columns after restarting the program in tasks the 3rd column appear again.
You mean the combined mode?
I will add a time for completion.

Corsair

Yes, in combined mode, there is no time until the WU is reported, if "report result immediately" is not activated the time of completion won't be near the report time.
Roses don't bloom on the sailor's grave

Corsair.

Corsair

Hi Fred,

is this normal??

Directorio de C:\Trabajo\BoincTasks\history

15/11/2009  13:25    <DIR>          .
15/11/2009  13:25    <DIR>          ..
15/11/2009  13:25                 0 dir.txt
15/11/2009  13:22             9.031 history_elenita.cvs
15/11/2009  13:21             9.022 history_elenita.cvs1
15/11/2009  13:21             8.896 history_elenita.cvs2
15/11/2009  12:19             1.660 history_sboat.cvs
15/11/2009  12:19             1.651 history_sboat.cvs1
15/11/2009  09:59             1.642 history_sboat.cvs2
15/11/2009  13:19             2.486 history_wolf.cvs
15/11/2009  13:19             2.486 history_wolf.cvs1
15/11/2009  12:19             2.354 history_wolf.cvs2
              10 archivos         39.228 bytes
               2 dirs  30.389.878.784 bytes libres

should be .CSV "comma separated values" ??

and why 3 copies of each??
Roses don't bloom on the sailor's grave

Corsair.

fred

Quote from: Corsair on November 15, 2009, 12:28:00 PM
Hi Fred,

is this normal??

Directorio de C:\Trabajo\BoincTasks\history

15/11/2009  13:25    <DIR>          .
15/11/2009  13:25    <DIR>          ..
15/11/2009  13:25                 0 dir.txt
15/11/2009  13:22             9.031 history_elenita.cvs
15/11/2009  13:21             9.022 history_elenita.cvs1
15/11/2009  13:21             8.896 history_elenita.cvs2
15/11/2009  12:19             1.660 history_sboat.cvs
15/11/2009  12:19             1.651 history_sboat.cvs1
15/11/2009  09:59             1.642 history_sboat.cvs2
15/11/2009  13:19             2.486 history_wolf.cvs
15/11/2009  13:19             2.486 history_wolf.cvs1
15/11/2009  12:19             2.354 history_wolf.cvs2
              10 archivos         39.228 bytes
               2 dirs  30.389.878.784 bytes libres

should be .CSV "comma separated values" ??

and why 3 copies of each??

http://www.efmer.eu/forum_tt/index.php?topic=154.0
Windows or the program can shut down any minute even when writing a file.
When this happens one of the backup files is used.

idahofisherman

Anansi 1034_0 does not show as completed in the history panel, instead it shows as updating only and reporting OK.  It never completes. As you can see in the messages panel everything looks like it completed okay.


709   anansi   11/14/2009 11:36:28 PM   Started download of anansi_1258243430_1034   
710   anansi   11/14/2009 11:36:29 PM   Finished download of anansi_1258243430_1034   
711   anansi   11/14/2009 11:36:29 PM   Starting anansi_1258243430_1034_0   
712   anansi   11/14/2009 11:36:29 PM   Starting task anansi_1258243430_1034_0 using anansi version 106   
713   anansi   11/14/2009 11:36:37 PM   Computation for task anansi_1258243430_1034_0 finished   
714   anansi   11/14/2009 11:36:37 PM   Sending scheduler request: To fetch work.   
715   anansi   11/14/2009 11:36:37 PM   Reporting 1 completed tasks, requesting new tasks   
716   anansi   11/14/2009 11:36:39 PM   Started upload of anansi_1258243430_1034_0_0   
717   anansi   11/14/2009 11:36:40 PM   Finished upload of anansi_1258243430_1034_0_0   
718   anansi   11/14/2009 11:36:57 PM   Scheduler request completed: got 1 new tasks   
719   anansi   11/14/2009 11:36:59 PM   Started download of anansi_1258243430_1040   
720   anansi   11/14/2009 11:37:00 PM   Finished download of anansi_1258243430_1040   
721   anansi   11/14/2009 11:37:00 PM   Starting anansi_1258243430_1040_0   
722   anansi   11/14/2009 11:37:00 PM   Starting task anansi_1258243430_1040_0 using anansi version 106   

Corsair

Hi Fred,

"Efficiency GPU __% warning when above. (100 = Disabled)"

until now I could not check it because with ATI optimized applications looks like
that doesn't work, but I have attached to Collatz Conjecture project where
there is a stock application for ATI, if the stock application is used in BW is shown
as GPU WU, I have set to 25% the GPU warning, but now I check it and there is
one error, because I want that error will be shown when the GPU efficiency is
below 25%, that means that is something strange if the GPU performance is
below such value.

so, should be defined and working as below:
"Efficiency GPU __% warning when below. (0 = Disabled)"

there is something that could be useful for future version of BT, when used optimized
application for ATI/AMD GPU there are consider by BT as CPU, if stock application exist
and used in one project BT considers as GPU task.

Why?? (I don't know)
Roses don't bloom on the sailor's grave

Corsair.

fred

Quote from: idahofisherman on November 15, 2009, 07:20:04 PM
Anansi 1034_0 does not show as completed in the history panel, instead it shows as updating only and reporting OK.  It never completes. As you can see in the messages panel everything looks like it completed okay.


709   anansi   11/14/2009 11:36:28 PM   Started download of anansi_1258243430_1034   
710   anansi   11/14/2009 11:36:29 PM   Finished download of anansi_1258243430_1034   
711   anansi   11/14/2009 11:36:29 PM   Starting anansi_1258243430_1034_0   
712   anansi   11/14/2009 11:36:29 PM   Starting task anansi_1258243430_1034_0 using anansi version 106   
713   anansi   11/14/2009 11:36:37 PM   Computation for task anansi_1258243430_1034_0 finished   
714   anansi   11/14/2009 11:36:37 PM   Sending scheduler request: To fetch work.   
715   anansi   11/14/2009 11:36:37 PM   Reporting 1 completed tasks, requesting new tasks   
716   anansi   11/14/2009 11:36:39 PM   Started upload of anansi_1258243430_1034_0_0   
717   anansi   11/14/2009 11:36:40 PM   Finished upload of anansi_1258243430_1034_0_0   
718   anansi   11/14/2009 11:36:57 PM   Scheduler request completed: got 1 new tasks   
719   anansi   11/14/2009 11:36:59 PM   Started download of anansi_1258243430_1040   
720   anansi   11/14/2009 11:37:00 PM   Finished download of anansi_1258243430_1040   
721   anansi   11/14/2009 11:37:00 PM   Starting anansi_1258243430_1040_0   
722   anansi   11/14/2009 11:37:00 PM   Starting task anansi_1258243430_1040_0 using anansi version 106   

instead it shows as updating only and reporting OK.
I'm not clear what you mean. The status is reported OK. And where does it show updating.

idahofisherman

#10
The example that matches the given message area has rolled off the history panel.  But there are many examples, here is one.


History Panel:

Updating ...   0.00 Updating Please wait    anansi 1258243430_54581 00:00:04  11/16/2009 1:38:14 AM  Report OK   elements

This entry stays in the updating mode for ever.  "Updating" should be replaced with anansi (application name) and "0.00 updating Please wait" should be replace with 1.06 anansi (execute module name).

Message Panel
Here are the messages that go with this WU.
elements

3220   anansi   11/16/2009 1:35:46 AM   Started download of anansi_1258243430_54581   
3221   anansi   11/16/2009 1:35:48 AM   Finished download of anansi_1258243430_54581   
3222   anansi   11/16/2009 1:35:48 AM   Starting anansi_1258243430_54581_1   
3223   anansi   11/16/2009 1:35:48 AM   Starting task anansi_1258243430_54581_1 using anansi version 106   
3224   anansi   11/16/2009 1:35:54 AM   Computation for task anansi_1258243430_54581_1 finished   
3225   anansi   11/16/2009 1:35:55 AM   Sending scheduler request: To fetch work.   
3226   anansi   11/16/2009 1:35:55 AM   Reporting 1 completed tasks, requesting new tasks   
3227   anansi   11/16/2009 1:35:56 AM   Started upload of anansi_1258243430_54581_1_0   
3228   anansi   11/16/2009 1:35:58 AM   Finished upload of anansi_1258243430_54581_1_0


I hope this makes it a little clearer.   

fred

Yes now I understand what's happening.

fred

Quote from: Corsair on November 16, 2009, 04:44:54 PM
Hi Fred,

"Efficiency GPU __% warning when above. (100 = Disabled)"

until now I could not check it because with ATI optimized applications looks like
that doesn't work, but I have attached to Collatz Conjecture project where
there is a stock application for ATI, if the stock application is used in BW is shown
as GPU WU, I have set to 25% the GPU warning, but now I check it and there is
one error, because I want that error will be shown when the GPU efficiency is
below 25%, that means that is something strange if the GPU performance is
below such value.

so, should be defined and working as below:
"Efficiency GPU __% warning when below. (0 = Disabled)"

there is something that could be useful for future version of BT, when used optimized
application for ATI/AMD GPU there are consider by BT as CPU, if stock application exist
and used in one project BT considers as GPU task.

Why?? (I don't know)
100 = disable is ok.
But only if the task is recognized as a GPU task.
So there should be (cuda) or (cal) or whatever just after the application name.
Another better check is in the filtered tasks it should say (gpu)
It may be that that CAL is still more or less Beta and not implemented as it should.

Corsair

Quote from: fred on November 17, 2009, 08:55:06 AM
100 = disable is ok.
But only if the task is recognized as a GPU task.
So there should be (cuda) or (cal) or whatever just after the application name.
Another better check is in the filtered tasks it should say (gpu)
It may be that that CAL is still more or less Beta and not implemented as it should.

I think that should be like CPU WU, so, 0 = disable is ok.

these GPU WU are recognized properly as gpu, at the end of the application name is shown:
- without filter "ati13ati"
- with filter and more than one WU "gpu", only one "ati13ati".

quite curious is if I use the stock application is fully recognised as GPU task in BT, but if I use
the optimized application with app_info.xml BT shows it as CPU task.

but the thing is if they are running (the stock one) and is running at 99% of GPU, correct, but
color is displayed as erroneous ratio GPU/CPU because I've set as 25%, this should means for
me if the ratio is below 25% should be coloured as erroneous but if it over this percentage should
means that everything  is going well.
Roses don't bloom on the sailor's grave

Corsair.

fred

Quote from: Corsair on November 17, 2009, 09:52:32 AM
Quote from: fred on November 17, 2009, 08:55:06 AM
100 = disable is ok.
But only if the task is recognized as a GPU task.
So there should be (cuda) or (cal) or whatever just after the application name.
Another better check is in the filtered tasks it should say (gpu)
It may be that that CAL is still more or less Beta and not implemented as it should.

I think that should be like CPU WU, so, 0 = disable is ok.

these GPU WU are recognized properly as gpu, at the end of the application name is shown:
- without filter "ati13ati"
- with filter and more than one WU "gpu", only one "ati13ati".

quite curious is if I use the stock application is fully recognised as GPU task in BT, but if I use
the optimized application with app_info.xml BT shows it as CPU task.

but the thing is if they are running (the stock one) and is running at 99% of GPU, correct, but
color is displayed as erroneous ratio GPU/CPU because I've set as 25%, this should means for
me if the ratio is below 25% should be coloured as erroneous but if it over this percentage should
means that everything  is going well.
That is because the app_info.xml is incorrect, or the task is a CPU one with GPU support.
<plan_class>ati</plan_class> or something similar.
And the class is used to distinguish between CPU and GPU.
No plan class is CPU, as it should be.