Is there a Way to split up gh/s between pools?

[jeppe]

Hi,
Im trying to test out different pools and only want to use a single miner for this. Is there a Way to split up gh/s in cgminer or a stratum proxy?? This must be how CEX.IO does it or how do they do it?
Thanks,
Jt

[Biffa]

You can do this with cgminer and the load-balance option and then set the quota in the pools

QUOTAS

The load-balance multipool strategy works off a quota based scheduler. The
quotas handed out by default are equal, but the user is allowed to specify any
arbitrary ratio of quotas. For example, if all the quota values add up to 100,
each quota value will be a percentage, but if 2 pools are specified and pool0
is given a quota of 1 and pool1 is given a quota of 9, pool0 will get 10% of
the work and pool1 will get 90%. Quotas can be changed on the fly by the API,
and do not act retrospectively. Setting a quota to zero will effectively
disable that pool unless all other pools are disabled or dead. In that
scenario, load-balance falls back to regular failover priority-based strategy.
While a pool is dead, it loses its quota and no attempt is made to catch up
when it comes back to life.

To specify quotas on the command line, pools should be specified with a
semicolon separated --quota(or -U) entry instead of --url. Pools specified with
--url are given a nominal quota value of 1 and entries can be mixed.

For example:
--url poola:porta -u usernamea -p passa --quota "2;poolb:portb" -u usernameb -p passb
Will give poola 1/3 of the work and poolb 2/3 of the work.

Writing configuration files with quotas is likewise supported. To use the above
quotas in a configuration file they would be specified thus:

"pools" : [
        {
                "url" : "poola:porta",
                "user" : "usernamea",
                "pass" : "passa"
        },
        {
                "quota" : "2;poolb:portb",
                "user" : "usernameb",
                "pass" : "passb"
        }
]

http://ck.kolivas.org/apps/cgminer/README

[jeppe]

You can do this with cgminer and the load-balance option and then set the quota in the pools

QUOTAS

The load-balance multipool strategy works off a quota based scheduler. The
quotas handed out by default are equal, but the user is allowed to specify any
arbitrary ratio of quotas. For example, if all the quota values add up to 100,
each quota value will be a percentage, but if 2 pools are specified and pool0
is given a quota of 1 and pool1 is given a quota of 9, pool0 will get 10% of
the work and pool1 will get 90%. Quotas can be changed on the fly by the API,
and do not act retrospectively. Setting a quota to zero will effectively
disable that pool unless all other pools are disabled or dead. In that
scenario, load-balance falls back to regular failover priority-based strategy.
While a pool is dead, it loses its quota and no attempt is made to catch up
when it comes back to life.

To specify quotas on the command line, pools should be specified with a
semicolon separated --quota(or -U) entry instead of --url. Pools specified with
--url are given a nominal quota value of 1 and entries can be mixed.

For example:
--url poola:porta -u usernamea -p passa --quota "2;poolb:portb" -u usernameb -p passb
Will give poola 1/3 of the work and poolb 2/3 of the work.

Writing configuration files with quotas is likewise supported. To use the above
quotas in a configuration file they would be specified thus:

"pools" : [
        {
                "url" : "poola:porta",
                "user" : "usernamea",
                "pass" : "passa"
        },
        {
                "quota" : "2;poolb:portb",
                "user" : "usernameb",
                "pass" : "passb"
        }
]

http://ck.kolivas.org/apps/cgminer/README

Will try this,
Thanks!!!!!
JT

[Und3rd0g]

I found that splitting between more that 3 pools produced very unpredictable/unstable results.

https://bitcointalk.org/index.php?topic=466307.msg5171506#msg5171506

Here are a few notes;

    Syntax:  Watch the syntax carefully it is unforgiving.
    Be sure to add the "load-balance" : true parameter.  It is not a default.
    When I started, I had a non-stratum server in my mix and performance slowed to a crawl.  I removed the non-stratum server from the pool of servers and performance went back to normal.  Need to do some additional homework on this.


In this example, I had 70% of my hashing power going to ghash.io, 20% to Bit Minter and 10% to BTC Guild.  I hope this helps anyone else who would need to divide up their hashing power among multiple pools.

--------- Start Example ---------
{
"pools" : [
   {
      "quota" : "70;stratum+tcp://us1.ghash.io:3333",
      "user" : "miner.1",
      "pass" : "AnyPassword"
        },

   {
      "quota" : "20;stratum+tcp://mint.bitminter.com:3333",
      "user" : "miner_1",
      "pass" : "AnyPassword"
   },
   
   {
      "quota" : "10;stratum+tcp://stratum.btcguild.com:3333",
      "user" : "minerX",
      "pass" : "AnyPassword"
   }
],


"load-balance" : true

}
--------- End Example ---------