![]() |
![]() |
#12 |
"Kieren"
Jul 2011
In My Own Galaxy!
27AC16 Posts |
![]() ![]() |
![]() |
![]() |
![]() |
#13 |
Mar 2019
USA
2F16 Posts |
![]()
Something clogging up the works this evening? Lots of 100% assignments hanging around having a party.
|
![]() |
![]() |
![]() |
#14 | |
"Kieren"
Jul 2011
In My Own Galaxy!
22×2,539 Posts |
![]() Quote:
![]() EDIT: "Overall" is back to the usual range. View Assignments is still high, but it always runs behind Overall. Last fiddled with by kladner on 2020-10-31 at 15:00 |
|
![]() |
![]() |
![]() |
#15 | |
"James Heinrich"
May 2004
ex-Northern Ontario
2×3×5×109 Posts |
![]()
Not related to any of the above, but there's now a warning at the top:
Quote:
|
|
![]() |
![]() |
![]() |
#16 | |
If I May
"Chris Halsall"
Sep 2002
Barbados
948110 Posts |
![]() Quote:
Rather than silently ignoring settings they used to accept, but don't any longer, they're now presenting these warnings. Since I'm "radiating", I haven't seen a GPU across any of my 13# Colab accounts since last Wednesday. And even the CPU-only instances last for only about 30 minutes each. Thanks for all the Factors Google. But, yeah, Colab is effectively dead-in-the-water for GPU72 efforts. ![]() |
|
![]() |
![]() |
![]() |
#17 |
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
7·19·37 Posts |
![]()
Strange. I have multiple non-gpu72 free Colab sessions going, and some just passed 4 hours of gpu now. A couple others ceased around the 6 hour mark. But I've noticed day of the week seems to matter.
Last fiddled with by kriesel on 2020-12-13 at 19:18 |
![]() |
![]() |
![]() |
#18 |
6809 > 6502
"""""""""""""""""""
Aug 2003
101×103 Posts
937210 Posts |
![]()
There is words to the effect of "lifetime usage limits". This is what I think is happening with regards to GPUs. On the account attached to my phone I got a T4 for about 45 minutes eariler today. It has far less hours on it than the other account that I have used.
|
![]() |
![]() |
![]() |
#19 | |
If I May
"Chris Halsall"
Sep 2002
Barbados
224118 Posts |
![]() Quote:
Just about every other GPU72_Colab Notebook user started having serious constraints well before I personally did. And, somewhat ironically, it was the Paid Tier who got shut-down first. I think it also has something to do with the Notebook being run, as there are reports of others continuing to have access to Colab GPU access using different code-paths. And, last data-set... A certain Greg continues to have access to four (4#) GPU72_Colab instances consistently, and others intermittently. Google, like ${DEITY}, acts in strange ways. Almost quantum (or, at least, intractable)... |
|
![]() |
![]() |
![]() |
#20 | |
Jan 2020
5·7 Posts |
![]() Quote:
Ditto here. I FINALLY get a GPU and this happens. ![]() ![]() Last fiddled with by mrk74 on 2021-01-08 at 16:12 Reason: Added info |
|
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Colab question | David703 | GPU to 72 | 279 | 2020-12-12 01:26 |
Revisiting msieve GPU with Colab | EdH | Msieve | 4 | 2020-08-24 02:22 |
GPU72 + Colab multiple assignments | windowfrog | GPU to 72 | 2 | 2020-07-07 19:47 |
Alternatives to Google Colab | kriesel | Cloud Computing | 11 | 2020-01-14 18:45 |
AVX2 Troubles with Colab Instance | EdH | YAFU | 5 | 2019-11-12 01:49 |