Also since the NY server is new, not many people have migrated over and it has very low load right now (only about 1.7GH vs 8 on the west coast server). That helps lower the rejects as well.

it is one rig with 4 gpus ... 
was making sure it was requesting enough for each gpu when just one btc username is used. thanks!

thanks! was trying to figure out the best way to do it in cgwatcher: profiles: arguments

current config arguments: getting ~940 Kh/s per gpu

--scrypt -o stratum+tcp://ny.clevermining.com:3333 -O username-btc:pass-x --gpu-platform 0 --worksize 256 --vectors 1 --intensity 20 --gpu-threads 1 --log 3 --thread-concurrency 33792 --lookup-gap 2 --api-port 4028 --expiry 120 --queue 1 --scan-time 60 --auto-fan --temp-target 95 --gpu-powertune 50 --gpu-memclock 1500 --gpu-engine 1000 --failover-only -o stratum+tcp://us.clevermining.com:3333 -O username-btc:pass-x

& was wondering about setting 1-2 gpu's for clevermining & 1 for ltc & 1 to test other pools ... w/ d- ?

would i need to repeat all the other settings per d- ? or do they get applied to all gpus unless otherwise specified?

thanks again, n-mine

or would comma seperated values work? gonna test it out ...

-d 0,1,2,3 -O username-btc0:pass-x0,username-btc1:pass-x1,username-btc2:pass-x3,username-ltc3:pass-x3

--scrypt -d 0,1,2,3 -o stratum+tcp://ny.clevermining.com:3333,stratum+tcp://useast.wafflepool.com:3333,stratum+tcp://useast.middlecoin.com:3333,stratum+tcp://united.wemineltc.com:3334 -O username-btc:pass-x --gpu-platform 0 --worksize 256 --vectors 1 --intensity 20 --gpu-threads 1 --log 3 --thread-concurrency 33792 --lookup-gap 2 --api-port 4028 --expiry 120 --queue 1 --scan-time 60 --auto-fan --temp-target 95 --gpu-powertune 50 --gpu-memclock 1500 --gpu-engine 1000 --failover-only -o stratum+tcp://us.clevermining.com:3333,stratum+tcp://uswest.wafflepool.com:3333,stratum+tcp://uswest.middlecoin.com:3333,stratum+tcp://usa.wemineltc.com:3336 -O username-btc0:pass-x0,username-btc1:pass-x1,username-btc2:pass-x3,username-ltc3:pass-x3

thanks!

nice! thanks!

found it in the faq:

"Q: Can I configure cgminer to mine with different login credentials or pools for each separate device?
A: No."

OMFG, you've just won the internet.. reading the FAQ.... wow!

FWIW, for those who don't know what a FAQ is it is Frequently Asked Questions. Emphasis on frequently.

Actually to clarify, Kalroth verified that cgminer code deferred to server derived settings for expiry, queue and scantime when those values are available versus what is set in your config/bat files.  

What gets buried in this thread is his statement that he doesn't know whether Clevermining's servers provide these settings as part of the stratum handshake.

In truth, most Altcoin pools do NOT pass these settings down to the client. So these settings can actually still be set on the clientside and have some effect since there are no server settings provided by the pool to default to.

Kalroth - feel free to chime in here to help clarify your statements further.

thanks Burnie! will try out load balancing

I agree. Before, it was vardiff, 16 to 1024, but for "technical issues" it was disabled. I think its about time you switched it back on.

That's actually reversed... the way the code is written is that the server settings takes precedence.  This was the point that Kalroth was making.

But that only holds true if the settings are actually delivered by the server, which in the case of this pool and quite a few others (I dare say most Altcoin pools), they are not.  At that point it's either your custom settings or the defaults builtin to CGMiner/SGMiner.

Just because they had minimal effect in your particular setup doesn't mean they won't work for someone else, especially when the server is not setting your q, e, s for you.