Bitcoin Forum
December 13, 2024, 04:22:50 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: 1 worker or many workers in solo pool  (Read 965 times)
PrivacyBTC (OP)
Newbie
*
Offline Offline

Activity: 54
Merit: 0


View Profile
April 22, 2015, 07:03:09 PM
 #1

Hello ALL

I need Urgent Answer from pool operator or Expert User

I have 6 Miners linked to SOLO POOL

Can I use 1 worker for 6 miners or 6 workers for 6 miners  (1 worker for 1 miner ) ?

we are in solo pool searching only for best shares so if 6 Miners with 1 worker generate different shares so may it be not good for pool to track that worker .

and if i split workers i will have low hashrate for every worker and i will got best share in longer time .

I hope u all reply with yours knowledge
Thanks
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1024


Mine at Jonny's Pool


View Profile WWW
April 22, 2015, 07:06:21 PM
 #2

It really doesn't matter.  It's your total hash that matters, not in how it's accomplished.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
-ck
Legendary
*
Offline Offline

Activity: 4312
Merit: 1649


Ruu \o/


View Profile WWW
April 22, 2015, 09:06:31 PM
 #3

It makes no difference to your chance of finding a block. The only reason to use different workers is so you can monitor their performance separately.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
aurel57
Legendary
*
Offline Offline

Activity: 1302
Merit: 1001



View Profile
April 22, 2015, 11:37:44 PM
 #4



Its like buying 6 chances on the lotto and either putting them on one ticket or 6 different tickets, it does not change things.
philipma1957
Legendary
*
Offline Offline

Activity: 4340
Merit: 9023


'The right to privacy matters'


View Profile WWW
April 23, 2015, 12:37:11 AM
 #5

It makes no difference to your chance of finding a block. The only reason to use different workers is so you can monitor their performance separately.


@ op this is the best answer and if anyone should know it is the guy that wrote the code and owns a solo pool.


I find if you have 6 machines   you can do two btc addresses each with 3 machines.

  If one goes down the number will be off by enough to figure something is wrong.


If 6 are lumped together and one goes down you could miss it.

▄▄███████▄▄
▄██████████████▄
▄██████████████████▄
▄████▀▀▀▀███▀▀▀▀█████▄
▄█████████████▄█▀████▄
███████████▄███████████
██████████▄█▀███████████
██████████▀████████████
▀█████▄█▀█████████████▀
▀████▄▄▄▄███▄▄▄▄████▀
▀██████████████████▀
▀███████████████▀
▀▀███████▀▀
.
 MΞTAWIN  THE FIRST WEB3 CASINO   
.
.. PLAY NOW ..
GreydonIselmoe
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


Credits [CRE] - Community Manager


View Profile WWW
April 23, 2015, 03:09:13 AM
 #6

It makes no difference to your chance of finding a block. The only reason to use different workers is so you can monitor their performance separately.


@ op this is the best answer and if anyone should know it is the guy that wrote the code and owns a solo pool.


I find if you have 6 machines   you can do two btc addresses each with 3 machines.

  If one goes down the number will be off by enough to figure something is wrong.


If 6 are lumped together and one goes down you could miss it.

This. Seeing how there's really no difference, you're better off just using separate workers so you can monitor each. However, you're chances of finding a block with 6 miners (Unless you have access to some crazy new rig) is probably slim to none. Regardless, best of luck to you!

████████  The next evolutionary step in crypto-currency | Sidechain technology - Claimable - sha256   ███████
████████████████  C R E D I T S - [C R E]  ███████████████
◥ Proof of Work / Proof of Deposit mining system ◥ Official Website ◥ Bitcointalk Thread ◥ Exchange
notlist3d
Legendary
*
Offline Offline

Activity: 1456
Merit: 1000



View Profile
April 23, 2015, 03:19:42 AM
 #7

Depending on pool I think many workers is better.  It allows difficulty to go to a specific miner, don't have to worry about it having a jumble.

And best is finding if you have a slowdown what is actually causing it.  With 1 worker you would have no idea what to check.  I personally use the last IP numbers as worker makes it very easy to find what's wrong.
kano
Legendary
*
Offline Offline

Activity: 4634
Merit: 1851


Linux since 1997 RedHat 4


View Profile
April 23, 2015, 03:46:10 AM
 #8

Depending on pool I think many workers is better.  It allows difficulty to go to a specific miner, don't have to worry about it having a jumble.
...
That doesn't matter with ckpool.
Each connection gets it's own difficulty already, even if they are the same worker.

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
kano
Legendary
*
Offline Offline

Activity: 4634
Merit: 1851


Linux since 1997 RedHat 4


View Profile
April 23, 2015, 03:47:45 AM
 #9

It makes no difference to your chance of finding a block. The only reason to use different workers is so you can monitor their performance separately.


@ op this is the best answer and if anyone should know it is the guy that wrote the code and owns a solo pool.


I find if you have 6 machines   you can do two btc addresses each with 3 machines.

  If one goes down the number will be off by enough to figure something is wrong.


If 6 are lumped together and one goes down you could miss it.
Don't forget that each worker also has web stats.
So you can still use one address but with a different worker name for each miner.

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
PrivacyBTC (OP)
Newbie
*
Offline Offline

Activity: 54
Merit: 0


View Profile
April 23, 2015, 09:45:15 AM
 #10

Sorry all , I didnt got a right answer  while the problem is

Miner 1 worker A  make 1.000.000  best share
Miner 2 worker A  make 3.000.000  best share
Miner 3 worker A  make 20.000.000 best share

In solo pool what is the right best share for worker A (Real best share )  ?

and if Miner 3 down did the pool still save his best share ?
aurel57
Legendary
*
Offline Offline

Activity: 1302
Merit: 1001



View Profile
April 23, 2015, 09:50:46 AM
 #11

Sorry all , I didnt got a right answer  while the problem is

Miner 1 worker A  make 1.000.000  best share
Miner 2 worker A  make 3.000.000  best share
Miner 3 worker A  make 20.000.000 best share

In solo pool what is the right best share for worker A (Real best share )  ?

and if Miner 3 down did the pool still save his best share ?

Why are you worrying about best shares? It does not mean a thing unless you do 47,610,564,513+ then you get a block of 25BTC anything under that share means nothing other than to show you how close you came, which can drive you nuts if it was close.
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1024


Mine at Jonny's Pool


View Profile WWW
April 23, 2015, 12:14:58 PM
 #12

Sorry all , I didnt got a right answer  while the problem is

Miner 1 worker A  make 1.000.000  best share
Miner 2 worker A  make 3.000.000  best share
Miner 3 worker A  make 20.000.000 best share

In solo pool what is the right best share for worker A (Real best share )  ?

and if Miner 3 down did the pool still save his best share ?
Who cares?  The shares are completely irrelevant until one of them exceeds the target network difficulty.  To answer your question, yes, the pool does save your best share.  For example, we lost power at my house a few nights ago.  My rPi didn't automatically restart cgminer (yeah, I should probably fix that), so my 5 U2s are not currently mining.  Yet, here is what is shown from ckpool:
Code:
{"hashrate1m": "0", "hashrate5m": "0", "hashrate1hr": "0", "hashrate1d": "0", "hashrate7d": "0", "lastupdate": 1429712208, "workers": 0, "bestshare": 5211017.239969668}

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!