Run the Lunatics installer 0.39 first and finnish a couple work units.
Will look into your results afterwards and tell you what to change.

Mike

...
What if I increased the cache size (16MB in and 16 MB out)? Would that help, or hinder?

I don't understand what cache you're referencing.

                                                                   Joe

RAC at either project is nearly meaningless at this point, since the computer has only been in use for a week or so.

The best indication now on how well the CPU is doing is to compare its performance against wingmates. WU 3526282 at Beta, for instance, matched your CPU against an Intel core i7 975 apparently running with hyperthreading on. There's no way to know if that i7 is overclocked or not, though, and it being ~7% faster on that one WU is probably within the range of variation caused by other tasks being done on the system.

In particular, your computer was probably doing 6 nearly identical VHAR tasks at that time, the i7 had a mix of work. It has been known for a long time that doing multiple VHAR tasks causes noticeable slowdown even on dual core CPUs, likely because VHAR tasks spend a larger fraction of the run time doing chirps and FFTs, both of which involve an 8 MiB input array and 8 MiB output array. IOW, even with relatively large cache there has to be a lot of transferring to/from RAM, and with multiple cores there's a lot of contention for both cache and RAM access.

All in all, I think your CPU is doing quite well. The next level of overclocking when you get the new cooler installed will certainly improve that more, but don't be surprised if a 9% further overclock (3.66 -> 4.0 GHz.) increases crunching performance less. Seeing if you can increase memory bandwidth might be helpful.

                                                                 Joe

I'm not sure Beta is ever short of work like the main project is at the moment. I was running S@H and Beta on a 4 core machines and I wanted 25% to Beta. However sometimes enough work would build up in Beta that it wasn't able to download any S@H work. My resource share setting are S@H 100 Beta 4. Since it wasn't working like I wanted I decided to run two instances of BOINC on that machine. With one instances limited to 3 CPU's and the other limited to 1. That way if the main project runs out of work it won't fill the queue up with Beta work.

Edit: Also what I meant about patience is that that machine shows it was "created" Sept. 5th 2011. When you said "I should be pushing near 10x that" you should know that your RAC will climb over time and you won't see anything near your average for a few weeks. Some say a few months.

For ATI apps you always have to change number of instances and count values.
All apps are OpenCL versions.
Not only for astropulse.

-instances_per_device 2
count 0.5

for running 2 paralell.

-instances_per_device 3
count 0.33

for 3
and so on.