Ben Berman03/29/2023, 11:13 PM
Stephen Bailey03/30/2023, 1:04 AM
, op tags, and the helm deployment chart.
Simon Frid03/30/2023, 2:13 AM
Stephen Bailey03/30/2023, 2:24 AM
Andrea Giardini03/30/2023, 7:10 AM
Ben Berman03/30/2023, 5:16 PM
but combining all sorts of data issues, network failures, stuck threads, zombie subprocesses, index errors, loading speeds@Simon Frid how much of this do you attribute to (1) dagster specifically (2) something else, like python (3) and the alternative, dagster's cloud offering? is 3 knowable?
schrockn03/30/2023, 5:18 PM
Ben Berman03/30/2023, 5:19 PM
For larger organizations becoming a Cloud user is the way to ensure a successful outcome at scale.we're not at a point yet where we know if there's any ROI to any of this. if we did, yeah, i'd just use the cloud offering, because then the math would be straightforward
Simon Frid03/31/2023, 2:27 AM
Andrea Giardini03/31/2023, 7:13 AM
that is what i found most frustrating about elastic. there’s clearly a file that they use for their configuration, which is not at all proprietary. it would cost them nothing to shareIMO it won’t be very helpful for them to share. Sure, they have a config file, and sure it’s optimized, but it’s optimized to their infrastructure and their setup. The same config file in your infra will most probably perform badly on not perform altogether. I worked for open-source companies before (companies doing OSS software with an enterprise offering), and this is the most difficult message to come across to OSS community: when you pay for a cloud solution, you are paying for a highly-optimized environment built by the same developers that are providing you the software. These people know the ins and outs of the software and know how to tune every single knob. They simply know the conditions in which it will perform best, and they know where to look whenever things go south. Could they share the configuration of our cloud offering with the OSS community? Sure. Would it be helpful or useful to somebody? Most definitely no because your infrastructure is different