cperry

15 ms·

31.
by cperry 3y ago
we'll start on Pro+, but plan to support Pro as well, including w/ autocompletions (those may slip if cost/usage comes in too high, but so far in dogfooding it's very reasonable).
32.
by cperry 3y ago
appeal in product and we're usually pretty forgiving
33.
by cperry 3y ago
gotta start somewhere. we're in a sprint this week working on different UX patterns.
34.
by cperry 3y ago
We had a couple SWEs move us from 3.7 to 3.10 over the past six months, removing years of tech debt. This comment is dead wrong. We'll upgrade to 3.11 when they push their final regular bug fix release in April 2024. Make fun of my stu
35.
by cperry 3y ago
Which one? If you're talking Palm 2, I couldn't say, I spend my days trying to convince everyone at Google to prioritize and support ME first ;)
36.
by cperry 3y ago
+1 all Colab files are the standard Jupyter .ipynb extension: we very much want to avoid any notion of lock-in. We bundle them all into a folder for you in Drive: it takes you like a second to take all of your work to any competitor.
37.
by cperry 3y ago
right back at you, thanks!
38.
by cperry 3y ago
I like the way you think
39.
by cperry 3y ago
not yet available; it'll roll out sequentially in the coming weeks as we sort out capacity and polish.
40.
by cperry 3y ago
lol been working on this since 2021; I have a small team and we do our best.
41.
by cperry 3y ago
we debated this; this is going to be a sequential rollout based on availability/capacity, and it seemed better to broadcast it was coming earlier b/c we're not going to have a "launch event" moment.
42.
by cperry 4y ago
I do not anticipate changes in the short term, but I am always open to changes in the medium term. Both of those address angles of abuse that I don't want to discuss in big forums, and go counter to interactive notebook compute, our to
43.
by cperry 4y ago
> I think this is one of the reasons Google is switching to this model. By far, the biggest user complaint I get is "why can't I access a GPU" which this change will address.
44.
by cperry 4y ago
I aspire to offer that level of transparency. I am foiled by (1) GPU prices can change randomly on me, and (2) it's hard to convey to a user pricing without giving them a huge incomprehensible price sheet. All is not lost though, I&#x2
45.
by cperry 4y ago
Sept 29 we'll have an announcement. Working on a blog post now that hopefully (?) will resolve some open questions.
46.
by cperry 4y ago
It's a fair critique and one we have discussed. With this change we are extending the lifetime of the units to three months to give users more flexibility. This is a net user improvement, today if you pay for a subscription any "u
47.
by cperry 4y ago
Will add to my list, thanks!
48.
by cperry 4y ago
You're always getting the whole card, never a slice fwiw. We haven't found a GPU virtualization solution that has a strong enough security boundary between slices, so we keep you isolated. And yes, hoping to give you more control
49.
by cperry 4y ago
Thanks! Colab has always had a notion of quota for all users. This notion was implemented in a hard to describe way, but we would throttle you as you used more compute without making it clear how or why. This change will make the quota allo
50.
by cperry 4y ago
I hope it works better for you, please send feedback if it doesn't!
51.
by cperry 4y ago
Thanks! Grand majority of paid users will see no impact to their limits. We do have some bugs where a small fraction of paid users today use more than their quota (Pro+ users burning $100 worth of an A100 when paying us $50), and those folk
52.
by cperry 4y ago
Thanks! I think people will much prefer this over the current opaque system. I read every feedback submission in Colab so if you ever have feedback you'd like addressed, send away.
53.
by cperry 4y ago
I'll refund you myself if you hate it. This change will give you more transparency in your paid compute consumption, though won't land for 30 days.
54.
by cperry 4y ago
Why thank you!
55.
by cperry 4y ago
This increases visibility into your paid compute consumption. Net win for folks. Feature doesn't launch for 30 days, but I can't make any changes like this without changing ToS, which I have to pre-announce.
56.
by cperry 4y ago
My peeps, I cannot get legal counsel for seventy billion countries to turn around a ToS update this fast. This has been planned for months, we're looking to increase transparency in your paid compute consumption.
57.
by cperry 4y ago
The change is meant to provide increased visibility in your paid compute consumption.
58.
by cperry 4y ago
PM for Colab - I wrote the email. No intention to lock it down? Whatever that would mean? We ensure notebooks are totally portable for any other Jupyter install you want to move to. This change is about laying the groundwork for increased t
59.
by cperry 4y ago
Thank you!!
60.
by cperry 4y ago
Makes sense. I won't get to it soon, but try to bump that age limit down when I get a chance.

More ›