oavdeev

I have once built an interactive calculator[1] for this exact problem, maybe someone else will find it useful too

[1] https://observablehq.com/@oavdeev/parallel-task-latency-calc...

oavdeev

8 年前議論

Yeah QuickSight is their shot at that market. But (anecdotally) I don't think it getting much traction. The fact that they didn't have any flashy announcements about it at re:Invent this year somewhat corroborates that. There is something in Amazon DNA that prevents them from building great UX-centric products.

Besides, without something like Google Sheets or Excel it is not that useful, inevitably you have a ton of small data across the org that is stored in spreadsheets.

One obvious play for Amazon is to just pay a ton of cash and acquire something like Airtable, but they don't seem to be for sale.

oavdeev

8 年前議論

That set of people is not that small; it is basically what people in business analyst roles do all day. They know Excel very well and maybe even a bit of python/js, have a good understanding of the business problem at hand, but not technical enough to do full on custom reports from scratch.

Data Studio fits squarely in this market of tools for them, and that space is growing and pretty crowded. There a multiple big businesses built on producing tools just like that, for example Tableau (public company valued at ~10B as of today).

Granted, Data Studio is more basic but it is free and nicely integrates with the rest of Google data product suite (Analytics, Sheets, BigQuery). I don't think it will go away, and I think it is actually the strongest part of google cloud offering (and the biggest gap in AWS cloud product lineup).

oavdeev

8 年前議論

It does; unfortunately they don't have a nice way to just disallow overwrites (that's why I was curious how you implemented that)

oavdeev

8 年前議論

How did you do "no overwrite" bit? By enabling versioning?

oavdeev

8 年前議論

I suspect it works well for business travellers though; they are not that price sensitive (as long as the fare is within the company policy).

oavdeev

8 年前議論

Here's lstopo output for the largest one, for good measure: https://instaguide.io/info.html?type=a1.4xlarge#tab=lstopo though there's nothing terribly surprising.

oavdeev

8 年前議論

Here's lstopo output on a 4-core AWS instance to illustrate your point: https://instaguide.io/info.html?type=c5.xlarge#tab=lstopo

oavdeev

8 年前議論

If you're using AWS anyway, I think using their managed Postgres / RDS could make this a lot easier operationally. No need for custom syncing/backup scripts, easier to scale the storage up.

To the larger point, while I totally agree with the premise -- most apps will never need to scale beyond one large instance, I'm not exactly sure what's the actual tradeoff is. If you're writing a simple CRUD app, it is not really controversial that it shouldn't need any complex distributed stuff anyway, it is just a simple python/Go app and a data store.

Most "fancy" things outside that single process paradigm, such as avoiding using local disk and using S3/RDS/document stores, using containers for deployment, etc. usually have more to do with making the app operationally simpler and easy to recover from instance failures than scaling per se.

oavdeev

8 年前議論

To be fair, AWS gives you bigger discounts for RI than GCP's sustained use. That makes sense; someone gotta pay for the risk.

This said, GCPs committed use discounts still seem to be a better deal than convertible RIs.

Looking at the run-of-the-mill 64GB RAM standard instance:

  AWS 1yr all upfront:            $0.458
  GCP commited use:               $0.47878
  AWS 1yr no upfront:             $0.491
  GCP sustained use:              $0.532
  AWS 1yr no upfront convertible: $0.564

edit: confused commited vs sustained use for a second there

oavdeev

8 年前議論

I mean.. I get it, there isn't a lot to work with, it is a thing that _stores files_ after all, and it most closely resembles a normal filesystem.

But it does make GCP's storage product naming even more confusing overall (after "Cloud Storage" vs "Cloud Datastore" mentioned above).

oavdeev

8 年前議論

So now they have two cloud storage products, called Cloud Firestore and Cloud Filestore? Their branding team is on top of their game, as always.

oavdeev

8 年前議論

You're talking about a hypothetical fund with 20/20 hindsight.

oavdeev

8 年前議論

Alpine.ai | ML engineer, Full Stack engineer | San Francisco | ONSITE

We're well-funded, early stage startup in SF. You have a chance to join our team as one of the founding engineers.

Did you know that Amazon Echo is the best selling product on all of Amazon this holiday season? We're building a platform for conversational product search, to make these 450M voice-enabled devices home for brands and big e-commerce players.

If you're a senior machine learning engineer (ideally, with experience or interest in NLP), or a full stack engineer who wants to work on our ML platform -- we'd love to talk to you.

Check out open positions at our website https://alpine.ai/careers/. Happy to tell you more by email [email protected] or over a coffee.

oavdeev

8 年前議論

Alpine.ai | San Francisco | ML and full stack engineers | ONSITE

Did you know that Echo is the best selling product on all of Amazon this holiday season? We're building a platform for conversational product search, to make these 450M voice-enabled devices home for brands and big e-commerce players.

We're well-funded, early stage startup in SF. You have a chance to join our team as one of the founding engineers.

If you're a full stack engineer who wants to work on our ML platform, or a senior machine learning engineer -- ideally, with experience or interest in NLP -- we'd love to talk to you.

Check out open positions at our website https://alpine.ai/careers/. Happy to tell you more by email [email protected] or over a coffee.

投稿

Agentic Metaflow

How to compute latency of N parallel requests

Parallel Task Latency Calculator

vPMU support on EC2 and the weird case of z1d instance family

/proc/cpuinfo and CPU topology for all 113 AWS instance types

Trck: querying discrete time series with state machines

コメント