[ANN][AUTO-SWITCH] Profit-switch auto-exchange pool: CleverMining.com

[eclipso]

Thank you for US East Server.   0% reject after 2 hours and going!!!!

Soooo all this talk about the rejects being the fault of inexperienced miners goes out the window when a simple server change removes rejects.

That's basic troubleshooting 101 and some folks here spouting BS about inexperienced miners need to offer up some apologies...

[Shastada]

Thank you for US East Server.   0% reject after 2 hours and going!!!!

Soooo all this talk about the rejects being the fault of inexperienced miners goes out the window when a simple server change removes rejects.

That's basic troubleshooting 101 and some folks here spouting BS about inexperienced miners need to offer up some apologies...

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.

[solariis]

I've been on the NY server all night but my 'ready for payout' balance seems really low (0.002 instead of 0.01). Anyone else having this issue?

Yes, I started having this problem yesterday in fact. My balances used to update every time the hash rate updated on the charts (every 10 minutes). Now I can go hours without seeing an update in my ready for payout, unexchanged, total expected and total profits. I'm not certain if the 1 Mh/s i'm doing during these times is being neglected or if the site is just updating less regularly. Either way, it's a concern to me. If I start seeing less than the advertised payout come through (right now it's .00650 BTC/day/Mh) then I will have to reconsider using this pool soon.

[n_mine]

hi clevermining crew!

how are you?

is it ok to point 4 gpus with one btc address on your pool or should i have a separate btc for each one?

i have cgwatcher running cgminer & am getting 3-4 MH/s but only seeing ~.01 btc payout every 24 hours & seems like it should be 2-3 times more ...

& does anyone know the miner arguments for adding different usernames/passwords & even pools for each gpu?

is it?:

d- 0 -u name p- password d- 1 -u name p- password d- 2 -u name p- password d- 3 -u name p- password

thanks, n-mine

Do you mean multiple rigs or GPUs??? One BTC address for multiple miners works fine on this site.  Indivudual GPUs do not need their own un or password. The password itself doesnt matter (just put any value).

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!

[elpsycongro]

Thank you for US East Server.   0% reject after 2 hours and going!!!!

Soooo all this talk about the rejects being the fault of inexperienced miners goes out the window when a simple server change removes rejects.

That's basic troubleshooting 101 and some folks here spouting BS about inexperienced miners need to offer up some apologies...

i think its abit of both , lots of times it can be a bad config on the miner , but i did find my rejects went from 6% (after fixing config this is the lowest it will go) to 3% by switching to the east server, so yeah the server has something to do with rejects too.

[n_mine]

hi clevermining crew!

how are you?

is it ok to point 4 gpus with one btc address on your pool or should i have a separate btc for each one?

i have cgwatcher running cgminer & am getting 3-4 MH/s but only seeing ~.01 btc payout every 24 hours & seems like it should be 2-3 times more ...

& does anyone know the miner arguments for adding different usernames/passwords & even pools for each gpu?

is it?:

d- 0 -u name p- password d- 1 -u name p- password d- 2 -u name p- password d- 3 -u name p- password

thanks, n-mine

You can have multiple GPUs and machines (rigs) with the same username/address.

You should check your stats page. Especially hashrate/rejected and "Immature", "Unexchanged" and "Ready For Payout"

If I remember correctly, if you want to point each GPU to a specific pool and/or username, you have to start multiple cgminers
cgminer -d 0 -o http://pool1:port -u user1 -p pass1
cgminer -d 1 -o http://pool2:port -u user2 -p pass2
etc.

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

[pengoau]

The "only" config you can change for this pool is intensity and even then its not possible (e.g. 280x).

People pointing at your config, where totally underestimating how overloaded the (only) server was.

Some people had already good configs and after trying elsewhere got good performance and only when they were here they had high rejects. Higher than the expected 10%~ due to the coins that are mined...

Whats a bad config? What setting on the miner did you change? You know that queue, scan time and expiry have no affect and its all driven by the server.

In my subtle way and thanks to Kalroth, it was proved that really the only setting available to you is intensity.

[n_mine]

hi clevermining crew!

how are you?

is it ok to point 4 gpus with one btc address on your pool or should i have a separate btc for each one?

i have cgwatcher running cgminer & am getting 3-4 MH/s but only seeing ~.01 btc payout every 24 hours & seems like it should be 2-3 times more ...

& does anyone know the miner arguments for adding different usernames/passwords & even pools for each gpu?

is it?:

d- 0 -u name p- password d- 1 -u name p- password d- 2 -u name p- password d- 3 -u name p- password

thanks, n-mine

You can have multiple GPUs and machines (rigs) with the same username/address.

You should check your stats page. Especially hashrate/rejected and "Immature", "Unexchanged" and "Ready For Payout"

If I remember correctly, if you want to point each GPU to a specific pool and/or username, you have to start multiple cgminers
cgminer -d 0 -o http://pool1:port -u user1 -p pass1
cgminer -d 1 -o http://pool2:port -u user2 -p pass2
etc.

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!

[pengoau]

cgminer --help

[n_mine]

cgminer --help

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."

[Burnie]

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!

That will probably not do what you want.

I'm not familiar with cgwatcher, but you I think you also will have to run one cgwatcher for each cgminer. (And then use different api ports)

Before you start digging yourself into big and difficult configs, you haven't considering setting up simple load balancing rather than dedicating
devices to pools?

This will give 2/4 of the work to pool1, 1/4 to pool2 and 1/4 to pool3   (skip --url/-o and --failover-only)
  -U "2;pool1:port" -u user1 -p pass -U "1;pool2:port" -u user2 -p pass -U "1;pool3:port" -u user3 -p pass  ...

[pengoau]

cgminer --help

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.

[n_mine]

cgminer --help

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.

pretty sure you won!
sarcasm online - now that's a first! guess i need the /s font for my nice. thanks for the --help.

& wasting your time letting everyone know about --help & what acronyms are.

& thanks Burnie for an informative/useful reply. will try out load balancing.

[jedimstr]

The "only" config you can change for this pool is intensity and even then its not possible (e.g. 280x).

People pointing at your config, where totally underestimating how overloaded the (only) server was.

Some people had already good configs and after trying elsewhere got good performance and only when they were here they had high rejects. Higher than the expected 10%~ due to the coins that are mined...

Whats a bad config? What setting on the miner did you change? You know that queue, scan time and expiry have no affect and its all driven by the server.

In my subtle way and thanks to Kalroth, it was proved that really the only setting available to you is intensity.

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.

[pengoau]

The "only" config you can change for this pool is intensity and even then its not possible (e.g. 280x).

People pointing at your config, where totally underestimating how overloaded the (only) server was.

Some people had already good configs and after trying elsewhere got good performance and only when they were here they had high rejects. Higher than the expected 10%~ due to the coins that are mined...

Whats a bad config? What setting on the miner did you change? You know that queue, scan time and expiry have no affect and its all driven by the server.

In my subtle way and thanks to Kalroth, it was proved that really the only setting available to you is intensity.

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.

If you don't specify them the client uses the default setting, which if set by the server is used. After test I found using various settings including these didn't really help. Once I changed to the Asia server, performance improved. Proof is in the pudding, the US server at the time was overloaded it had nothing to do with a "bad config".

I was being reasonable to, I was willing to put up with no more than 10% rejects.

[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!

That will probably not do what you want.

I'm not familiar with cgwatcher, but you I think you also will have to run one cgwatcher for each cgminer. (And then use different api ports)

Before you start digging yourself into big and difficult configs, you haven't considering setting up simple load balancing rather than dedicating
devices to pools?

This will give 2/4 of the work to pool1, 1/4 to pool2 and 1/4 to pool3   (skip --url/-o and --failover-only)
  -U "2;pool1:port" -u user1 -p pass -U "1;pool2:port" -u user2 -p pass -U "1;pool3:port" -u user3 -p pass  ...

thanks Burnie! will try out load balancing

[rammy2k2]

you should lower pool diff , scryptguild has from 32 to 256 , clever has only 512 ....

[byt411]

you should lower pool diff , scryptguild has from 32 to 256 , clever has only 512 ....

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.

[rammy2k2]

you should lower pool diff , scryptguild has from 32 to 256 , clever has only 512 ....

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.

yea, please go back

[jedimstr]

The "only" config you can change for this pool is intensity and even then its not possible (e.g. 280x).

People pointing at your config, where totally underestimating how overloaded the (only) server was.

Some people had already good configs and after trying elsewhere got good performance and only when they were here they had high rejects. Higher than the expected 10%~ due to the coins that are mined...

Whats a bad config? What setting on the miner did you change? You know that queue, scan time and expiry have no affect and its all driven by the server.

In my subtle way and thanks to Kalroth, it was proved that really the only setting available to you is intensity.

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.

If you don't specify them the client uses the default setting, which if set by the server is used. After test I found using various settings including these didn't really help. Once I changed to the Asia server, performance improved. Proof is in the pudding, the US server at the time was overloaded it had nothing to do with a "bad config".

I was being reasonable to, I was willing to put up with no more than 10% rejects.

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.