search

mludvig / aws-ethereum-miner

CloudFormation template for mining Ethereum crypto currency on AWS
267 stars 152 forks source link

Workers not showing up although a total of 404 instances were created and active #56

Closed MoAdelAbdelrahman closed 2 years ago

MoAdelAbdelrahman commented 2 years ago

I created the stack and increased my limits, A total of 404 instances were created and running but workers are not shown? 31231 12321

MoAdelAbdelrahman commented 2 years ago

my account limits: 8 vcpu for X instances and 60 on demand.

mludvig commented 2 years ago

I see that you've changed the template to allow running r5a.large instances - these can't mine ETH. That's why they are not included in my template. You'll need to raise your service limits for P or G instances, these are the only one that can mine ETH.

MoAdelAbdelrahman commented 2 years ago

Thanks for the response, I managed to get an increase of 32Vcpus and I am running your template now, I just want to ask, how to check the hashrate reported by Ethimnier as stated in the repo?

Thank you

On Mon, Jun 13, 2022, 11:28 PM Michael Ludvig @.***> wrote:

Closed #56 https://github.com/mludvig/aws-ethereum-miner/issues/56 as completed.

— Reply to this email directly, view it on GitHub https://github.com/mludvig/aws-ethereum-miner/issues/56#event-6799365970, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN3VLCASUHCYPQTPYESWVW3VO6RZBANCNFSM5YVE7RQA . You are receiving this because you authored the thread.Message ID: @.***>

mludvig commented 2 years ago

What instance types has it started?

MoAdelAbdelrahman commented 2 years ago

G4ad.xlarge G5g.xlarge

A total of 11

On Tue, Jun 14, 2022, 10:53 PM Michael Ludvig @.***> wrote:

What instance types has it started?

— Reply to this email directly, view it on GitHub https://github.com/mludvig/aws-ethereum-miner/issues/56#issuecomment-1155701912, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN3VLCFYZWJ6LST4SIUXIVTVPDWK5ANCNFSM5YVE7RQA . You are receiving this because you authored the thread.Message ID: @.***>

mludvig commented 2 years ago

Cool, you should now see that they are mining on ethermine.org. It takes 15 to 20 minutes before they show up and then the reported hashrate will ramp up slowly because ethermine calculates an average every 10 mins. Give it at least 2 hrs to let it stabilise.

MoAdelAbdelrahman commented 2 years ago

Thanks, I see now its stable on around 360MH/s, Any idea how to increase that? Is it considered too low?

On Tue, Jun 14, 2022, 10:59 PM Michael Ludvig @.***> wrote:

Cool, you should now see that they are mining on ethermine.org. It takes 15 to 20 minutes before they show up and then the reported hashrate will ramp up slowly because ethermine calculates an average every 10 mins. Give it at least 2 hrs to let it stabilise.

— Reply to this email directly, view it on GitHub https://github.com/mludvig/aws-ethereum-miner/issues/56#issuecomment-1155707706, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN3VLCHRCHANRDVQZQ6OUWLVPDXERANCNFSM5YVE7RQA . You are receiving this because you authored the thread.Message ID: @.***>

MoAdelAbdelrahman commented 2 years ago

Please help me it took a lot of money from me here already, instances types are g4ad, g4dn, g5g.

On Wed, Jun 15, 2022, 7:36 PM Mohammed Adel @.***> wrote:

Hello, Mr Micheal, I really need help, how much instances should be running? Because there's 11 instances running here but it takes too much money and makes around 5 usd per day as estimated in Ethermine dashboard. What should I do?

On Tue, Jun 14, 2022, 11:01 PM Mohammed Adel @.***> wrote:

Thanks, I see now its stable on around 360MH/s, Any idea how to increase that? Is it considered too low?

On Tue, Jun 14, 2022, 10:59 PM Michael Ludvig @.***> wrote:

Cool, you should now see that they are mining on ethermine.org. It takes 15 to 20 minutes before they show up and then the reported hashrate will ramp up slowly because ethermine calculates an average every 10 mins. Give it at least 2 hrs to let it stabilise.

— Reply to this email directly, view it on GitHub https://github.com/mludvig/aws-ethereum-miner/issues/56#issuecomment-1155707706, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN3VLCHRCHANRDVQZQ6OUWLVPDXERANCNFSM5YVE7RQA . You are receiving this because you authored the thread.Message ID: @.***>

MoAdelAbdelrahman commented 2 years ago

Also is it normal to be only having 1 worker for 11 instances??

On Wed, Jun 15, 2022, 7:40 PM Mohammed Adel @.***> wrote:

Please help me it took a lot of money from me here already, instances types are g4ad, g4dn, g5g.

On Wed, Jun 15, 2022, 7:36 PM Mohammed Adel @.***> wrote:

Hello, Mr Micheal, I really need help, how much instances should be running? Because there's 11 instances running here but it takes too much money and makes around 5 usd per day as estimated in Ethermine dashboard. What should I do?

On Tue, Jun 14, 2022, 11:01 PM Mohammed Adel @.***> wrote:

Thanks, I see now its stable on around 360MH/s, Any idea how to increase that? Is it considered too low?

On Tue, Jun 14, 2022, 10:59 PM Michael Ludvig @.***> wrote:

Cool, you should now see that they are mining on ethermine.org. It takes 15 to 20 minutes before they show up and then the reported hashrate will ramp up slowly because ethermine calculates an average every 10 mins. Give it at least 2 hrs to let it stabilise.

— Reply to this email directly, view it on GitHub https://github.com/mludvig/aws-ethereum-miner/issues/56#issuecomment-1155707706, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN3VLCHRCHANRDVQZQ6OUWLVPDXERANCNFSM5YVE7RQA . You are receiving this because you authored the thread.Message ID: @.***>

mludvig commented 2 years ago

Hi @MoAdelAbdelrahman

  1. g4ad.xlarge can do ca 48 MH/s, both g5g.xlarge and g4dn.xlarge can do ca 25 MH/s. If you've got 11 instances running then with some mix of these instance types your 360 MH/s seems reasonable.

  2. you will see one worker per region, it's expected.

  3. eth mining is not profitable at the moment due to falling prices.

MoAdelAbdelrahman commented 2 years ago

Thank you so much for your response, one final question, and sorry for disturbing you, is there a way of limiting the instance creation? like I only need to initiate 5 instances not 11, how should I do that?

On Thu, Jun 16, 2022 at 4:15 AM Michael Ludvig @.***> wrote:

Hi @MoAdelAbdelrahman https://github.com/MoAdelAbdelrahman

1.

g4ad.xlarge can do ca 48 MH/s, both g5g.xlarge and g4dn.xlarge can do ca 25 MH/s. If you've got 11 instances running then with some mix of these instance types your 360 MH/s seems reasonable. 2.

you will see one worker per region, it's expected. 3.

eth mining is not profitable at the moment due to falling prices.

— Reply to this email directly, view it on GitHub https://github.com/mludvig/aws-ethereum-miner/issues/56#issuecomment-1157155975, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN3VLCCPY5CAWULKB4G2G3TVPKE4ZANCNFSM5YVE7RQA . You are receiving this because you were mentioned.Message ID: @.***>

MoAdelAbdelrahman commented 1 year ago

Hello, Mr Micheal, I really need help, how much instances should be running? Because there's 11 instances running here but it takes too much money and makes around 5 usd per day as estimated in Ethermine dashboard. What should I do?

On Tue, Jun 14, 2022, 11:01 PM Mohammed Adel @.***> wrote:

Thanks, I see now its stable on around 360MH/s, Any idea how to increase that? Is it considered too low?

On Tue, Jun 14, 2022, 10:59 PM Michael Ludvig @.***> wrote:

Cool, you should now see that they are mining on ethermine.org. It takes 15 to 20 minutes before they show up and then the reported hashrate will ramp up slowly because ethermine calculates an average every 10 mins. Give it at least 2 hrs to let it stabilise.

— Reply to this email directly, view it on GitHub https://github.com/mludvig/aws-ethereum-miner/issues/56#issuecomment-1155707706, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN3VLCHRCHANRDVQZQ6OUWLVPDXERANCNFSM5YVE7RQA . You are receiving this because you authored the thread.Message ID: @.***>