One of my cruncher is processing this particular AP-WU with unroll=16.


(ap_17ap11ac_B5_P0_00403_20110721_16078)

Memory use is 632MB; this is quite high in my opinion. It'll be interesting to see the blanking% when completed.

Edit:

Run time = 2,099.08 (~34mins)
Found 30 single pulses and 30 repeating pulses, exiting.
  percent blanked: 0.00

Anyone else experiencing very high memory use?

My wingman (CPU) is having 512mb system RAM, I wonder how he is doing...

terencewee*
Sicituradastra.

That was high....

I have like between 40-160MB of memory use for ATI ap....
I have not seen "very high" memory use.
I run on a Core2Duo with 2GB Ram and i always have like 0.4GB Ram Free

I use this cmd line...

<cmdline>-instances_per_device 2 -unroll 12 -ffa_block 8192 -ffa_block_fetch 4096</cmdline>

//TQ

---

TRuEQ & TuVaLu

CAL 1.4.1417 (VM)

This driver failed to work on my host. I would recommend to do downgrade to not-VM drivers like 11.2 until 11.8 (in which bugfix was promized) will be released.

CAL 1.4.1417 (VM)

This driver failed to work on my host. I would recommend to do downgrade to not-VM drivers like 11.2 until 11.8 (in which bugfix was promized) will be released.

I had some weird behavior on my i7-2600 with 8GiG 1333 DDR3,
7 CPDN WUs were running and 1 SETI Bêta MB WU and CPDN
was pauzed, with a message: wating for video memory?!
Also 2 Collatz C. each on 1 card. I messed up the app_info file
or forgot an executable. That was some weeks ago, though.

Also, memory usage was unusual high >42% ~3.5GByte,
I stopped BOINC 6.13.0, one CPDN WU kept running(?).
I do use the CAL 1.4 driver again.
About the 2 EAH5870s, load is always higher on the 1st card
(device=0), but does work OK.

---

CAL 1.4.1417 (VM)

This driver failed to work on my host. I would recommend to do downgrade to not-VM drivers like 11.2 until 11.8 (in which bugfix was promized) will be released.

I had some weird behavior on my i7-2600 with 8GiG 1333 DDR3,
7 CPDN WUs were running and 1 SETI Bêta MB WU and CPDN
was pauzed, with a message: wating for video memory?!
Also 2 Collatz C. each on 1 card. I messed up the app_info file
or forgot an executable. That was some weeks ago, though.

Also, memory usage was unusual high >42% ~3.5GByte,
I stopped BOINC 6.13.0, one CPDN WU kept running(?).
I do use the CAL 1.4 driver again.
About the 2 EAH5870s, load is always higher on the 1st card
(device=0), but does work OK.

From the Boinc 7 change log:

EXTRA WARNING

The new BOINC 6.13 range is using completely new, from the ground up written code for many of its parts. It is not to be used if you are not an alpha tester. It is not to be used on all of your machines, just on one. When it doesn't work, report your problems to the developers and return to the latest 6.12.recommended.

At this time we're specifically testing whether or not the new CPU/GPU scheduling code works without using debt, and if projects will fetch work.

This is not a version that you install and walk away from, it needs constant checking, including the use of all the correct client configuration flags. Make sure your log files are of sufficient size so you can log through the night.

Minimum required flags to report with are <cpu_sched_debug>, <rr_simulation>, <sched_op_debug>, <work_fetch_debug>

Boinc 6.13.0 was Extremely Buggy, Boinc 6.13.1 is also Extremely Buggy,

Claggy

Glad, you responded so quick, I'll go back to 6.12.26(?).
Safer, it does work, but has some strange errors, f.i.
1 CPDN kept running, when BOINC 6.13.0. was completely
shut, so I thought.

---

Thanks guys.

*smack-hand-on-face* I think this could be because the cruncher has got 12GB and I set it to use 85%. :)

This could also be a fluke as I usually see ~120-160 range; similar to those reported by TRuEQ & TuVaLu.

@Raistmer:
It's a dedicated cruncher and stable with all projects/WUs so far.
I'll stick to current version until 11.8.

Thanks again.

terencewee*
Sicituradastra.

Boinc 6.13.0 was Extremely Buggy, Boinc 6.13.1 is also Extremely Buggy

Thanks Claggy - I'll continue to use 6.12.33.

terencewee*
Sicituradastra.

Is there any chance that one could get the future boinc-client to not have the "boinc news tab" first. Put it last(to the right)

And I also want the "messages" tab back where it was. and not in "advanced/preferneces/messages" in a separate window...

Or does everyone like new "face" of 6.12.33

I am still in 6.10.60 due to this...


//TQ

---

TRuEQ & TuVaLu

Is there any chance that one could get the future boinc-client to not have the "boinc news tab" first. Put it last(to the right)

And I also want the "messages" tab back where it was. and not in "advanced/preferneces/messages" in a separate window...

Or does everyone like new "face" of 6.12.33

I am still in 6.10.60 due to this...


//TQ

I use 6.12.33 with BOINC Manager from 6.10.58

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Do you have a "new" tab where the "project" tab use to be??
And is the "message" tab gone from the front window in your version HAL9000??

//TQ

---

TRuEQ & TuVaLu

"new"=="news" tab

sorry

---

TRuEQ & TuVaLu

Never seen the Edit button in a message you'd just created? ;-)

And yes, News is new and Messages is now called event log, reachable through the menu.

Gruß,
Gundolf

Do you have a "new" tab where the "project" tab use to be??
And is the "message" tab gone from the front window in your version HAL9000??

//TQ

There are 2 parts to BOINC:
1] the BOINC-client (daemon/service) (no UI)
2] the BOINC-manager

So, you can run BOINC-6.12.23 client (daemon/service/non-UI) to get non-FIFO GPU scheduling but control/view the client by using a BOINC-manager from 6.10.xx (which do not have Event-Viewer in a separate window). You can even connect-to/control multiple BOINC-clients from a single "manager" like BOINCtasks.

terencewee*
Sicituradastra.

Do you have a "new" tab where the "project" tab use to be??
And is the "message" tab gone from the front window in your version HAL9000??

//TQ

There are 2 parts to BOINC:
1] the BOINC-client (daemon/service) (no UI)
2] the BOINC-manager

So, you can run BOINC-6.12.23 client (daemon/service/non-UI) to get non-FIFO GPU scheduling but control/view the client by using a BOINC-manager from 6.10.xx (which do not have Event-Viewer in a separate window). You can even connect-to/control multiple BOINC-clients from a single "manager" like BOINCtasks.

terencewee*
Sicituradastra.

Exactly right. Tonight I'll do a little write up and post it on my site as there are some variations depending on the OS you are running.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

No, I haven't....

I'll look for one.

Thx for enlightn me :)

//TQ


Now I saw it up to the right where the message number is ;)
LOL!!!

//TQ

---

TRuEQ & TuVaLu

I wonder how to run the client..6.12.33 in the 6.10.60 Boinc-manager...
I haven't seen a howto for that yet.....

But I'll continue to try get that mix to work since i want the old UI and the new sheduling...

//TQ

---

TRuEQ & TuVaLu

For users who do not like the new BOINC Manager, there is really no use for you to go back to an older version, as all the older versions are more broken than this version is.

You can easily run the new BOINC with an older BOINC Manager.

Just copy your present boincmgr.exe and boinc.dll to someplace safe, before you install the new version. Then after installing the new version, do not start it up, but exit the installer quietly, then copy your preserved boincmgr.exe and boinc.dll back to the BOINC directory. Overwrite with the new versions.

Now start BOINC in your normal fashion.

---

Thank you for the "howto".

//TQ

---

TRuEQ & TuVaLu