3 Kaggle accounts? Did you add 3 different phone numbers?

Careful about that, I created a 2nd account without adding any phone number just for the 10 cpu instances, and now they blocked both accounts.
I wrote to them and asked if they could open the main account again and just delete the 2nd account, but no response yet.

[QUOTE=ATH;530068]3 Kaggle accounts? Did you add 3 different phone numbers?

Careful about that, I created a 2nd account without adding any phone number just for the 10 cpu instances, and now they blocked both accounts.
I wrote to them and asked if they could open the main account again and just delete the 2nd account, but no response yet.[/QUOTE]

Oh it was 3 Google accounts under Colab. Two personal google accounts and one by the university. Maybe I should tune it down a notch. :smile:

How did you get P100 on Google Colab?

I'm only getting K80 every time, I don't even think I ever got a T4.

I always got P100 on Kaggle for the 30 GPU hours.

[QUOTE=ATH;530178]How did you get P100 on Google Colab?

I'm only getting K80 every time, I don't even think I ever got a T4.

I always got P100 on Kaggle for the 30 GPU hours.[/QUOTE]

At first I kept getting K80, now half the time I got assigned P100, surprised but not unwelcomed.

I've been getting P100s and T4s in my playing around with my GPU experiments a lot more frequently. I don't stay on too long at a time, though.

Maybe Google's like, 'well we are not using these machines and these guys are not mining btc so why not like them have it?' :smile:

That's probably not why though. It does feel like a `waste' using these P100 for TF on colab, instead I can be running at least DCs.

Yeaah.. joining the club, like somebody said, not unwelcome.

[ATTACH]21287[/ATTACH]

[QUOTE=dcheuk;530197]...That's probably not why though. It does feel like a `waste' using these P100 for TF on colab, instead I can be running at least DCs.[/QUOTE]

If it will give you the time! It might actually take much longer to run a DC this way instead of on a local GPU with [I]CUDALucas[/I]. Sometimes, I think maybe [I]Colab[/I] sees all we do as crypto-mining because of the high utilization.

[QUOTE=storm5510;530212]Sometimes, I think maybe [I]Colab[/I] sees all we do as crypto-mining because of the high utilization.[/QUOTE]

Doubt it.

Most CM involves connecting with a "hive", keeping in constant contact.

Little sense wasting any additional time (beyond the 99.999999999999...% already expected to be wasted) searching for the magic random plaintext which results in the coveted special-case hash, if it's already been found.

100% utilization of compute is quite common nowadays.

Thankfully, at least /some/ of it is productive and co-operative towards actual value...

[QUOTE=chalsall;530241]Doubt it.

Most CM involves connecting with a "hive", keeping in constant contact.

Little sense wasting any additional time (beyond the 99.999999999999...% already expected to be wasted) searching for the magic random plaintext which results in the coveted special-case hash, if it's already been found.

100% utilization of compute is quite common nowadays.

Thankfully, at least /some/ of it is productive and co-operative towards actual value...[/QUOTE]

I wonder how large the "hive" actually is? It doesn't seem practical to have thousands of single-instance processors, or more. Fewer processors with the ability to have a great many threads would seem more likely. After all, they would want to keep their electrical utility costs as low as possible.

[QUOTE=storm5510;530283]I wonder how large the "hive" actually is? It doesn't seem practical to have thousands of single-instance processors, or more.[/QUOTE]

No. Instead there are thousands of geographically diverse "peers", each with thousands of threads of compute wasting their time searching an effectively random problem space, consuming massive amounts of energy for very little actual reduction of enthalpy.

IMO, a beautiful thought experiment. But, empirically, some implementations don't scale terribly well...