Topic: Using several miner instances with the same worker on a pool (Read 504 times)
Yes because you should assign a different worker names to each miner.
you can the name. just assign a different suffix - worker.x1, worker.x2...'
that'll help you to keep track of what each worker is doing.
that'll help you to keep track of what each worker is doing.
Does anybody have any experience with multiple miners arrangement under the same worker name?
Say for example you have several miners available, some of them are slower (about 40 kh/s), some are faster (400-700 kh/s), and they are geographically in different locations.
Is it better to use the same worker in configs for those miners, or should I assign different worker names to every miner?
Say for example you have several miners available, some of them are slower (about 40 kh/s), some are faster (400-700 kh/s), and they are geographically in different locations.
Is it better to use the same worker in configs for those miners, or should I assign different worker names to every miner?
You better assign different worker names to keep track of them.
Does anybody have any experience with multiple miners arrangement under the same worker name?
Say for example you have several miners available, some of them are slower (about 40 kh/s), some are faster (400-700 kh/s), and they are geographically in different locations.
Is it better to use the same worker in configs for those miners, or should I assign different worker names to every miner?
Say for example you have several miners available, some of them are slower (about 40 kh/s), some are faster (400-700 kh/s), and they are geographically in different locations.
Is it better to use the same worker in configs for those miners, or should I assign different worker names to every miner?
Jump to: