That's a nice ~8% increase. The only bummer is that I still get 100% CPU usage.
ATI's implementation of OpenCL (but not nVidia's if I recall...) on Windows likes to use the CPU a lot,
for some reason. This is not a problem with any miner. You'll probably see 100% CPU use on any OpenCL app
you try to run on that card.
The next pair would use 'platform=1' and then the next pair would use 'platform=2'. Hopefully somebody can confirm this or correct it.
Speaking of ATI's implementation vs. nVidia's implementation, that's how you switch between them.
If you have multiple "platforms" installed, (which usually only happens when you have both nVidia and ATI cards in the same system),
Phoenix will require
you to tell it which platform you want to use.
If it's not yelling at you to select a platform, you can get away with not setting it. To Phoenix (and the rest of the OS in general), a 5970
is no different from putting two 5870s in your system, so if you were to run a dual-5970 rig, you would address all 4 GPUs with DEVICE=0...3
Confusing, does OS and/or server location affect the hashrate?
I'm not sure what you mean about "server location" - where on the mining rig you extracted Phoenix? No, there's no reason that would affect hashrate.
Or did you mean the distance between your mining rig and the pool server? That shouldn't affect hashrate either, since Phoenix queues work.
OS does affect hashrate. It seems ATI Stream runs faster on Linux than elsewhere.
I just tested with:
phoenix.py -u http://jedi95.worker
:email@example.com:8332 -k poclbm FASTLOOP VECTORS BFI_INT PLATFORM=1 DEVICE=0 AGGRESSION=8
It works fine for me. What command line are you using?
Don't forget to include an askrate if you're on any [RPC] server! (You are fine excluding it on [MMP] and [RPC (+LP)] servers)
Something to note about how Phoenix parses URLs: You must include the trailing / if you want to use an askrate.
Phoenix sees http://mining.bitcoin.cz:8332;askrate=10
Will have problems loading the page.
Phoenix sees http://mining.bitcoin.cz:8332/;askrate=10
Will work correctly.
This is a problem with how urlparse parses the URL internally and I'm thinking of a way to better handle this now.