ozgune

14 ms·

121.
by ozgune 9y ago
(Ozgun from Citus) Citus extends PostgreSQL to make it a distributed database. In comparison, Cockroach builds the entire database from scratch and provides over the wire compatibility. For our users, this means that they get the following
122.
by ozgune 9y ago
I wanted to drop a semi-related note. Today is Enrico Fermi's birthday: https://en.wikipedia.org/wiki/Enrico_Fermi
123.
Fermi Estimates on Postgres Performance(citusdata.com)
56 points by ozgune 9y ago|5 comments
124.
by ozgune 9y ago
(quick additional note) If you're looking to use Citus Community edition for your multi-tenant project, one thing to keep in mind is how you set up replication. Citus comes with two replication methods: streaming and statement replicat
125.
by ozgune 9y ago
Hey Dan, nice to hear from you! > our prod base backups take 36 hours to restore, so if the recovery speed improvements are as advertised, that's a big win. Yes, if you attach 16TB of storage to each instance, your back-up restores
126.
by ozgune 9y ago
(Ozgun from Citus Data) > Whenever I've heard the term "sharding" it's usually in reference to the application-level sharding described in the article. I wanted to drop a quick clarification note here. In the article,
127.
by ozgune 9y ago
Reading through your comment again, I realize I completely missed the mark on your question. If you use Citus, you don't have to make any changes in your application. You just need to remodel your data and define your tables' shar
128.
by ozgune 9y ago
I used to think similarly several years ago. I now think differently for the following reasons: * Citus and other technologies can now provide features that do a lot of the heavy lifting. Some examples are resharding, shard rebalancing, and
129.
by ozgune 9y ago
Thanks for your input (also the_duke)! If time permits, we may come up with a second blog post on this topic. If I understood your example query, your application serves vendors and each vendor has different products. Is that correct? You c
130.
by ozgune 9y ago
Timeframes for sharding projects vary quite a bit. If you have a B2B database, we find that sharding projects usually take between one to eight weeks of engineering (not clock) time. Most take two to three weeks. A good way to tell is by
131.
by ozgune 9y ago
Hey everyone, it's Ozgun. When I first wrote this blog post, it was much longer. Based on initial feedback, I edited out parts of it to keep the post focused. If you have any questions that aren't covered in the post, happy to ans
132.
Why do engineers worry about scaling?(hackernoon.com)
2 points by ozgune 9y ago|0 comments
133.
by ozgune 9y ago
+1. Many large scale projects (for example the Boeing 787) end up over-budget and with delays. Does anyone have statistics on how projects of similar complexity performed in terms of their budgets and timelines?
134.
by ozgune 9y ago
(Ozgun from Citus) TLDR: We're thinking about multi-shard transactions and we'll share more updates as our timelines become concrete. In the 7.0 release cycle, we're looking at prototyping work on distributed deadlock detecti
135.
by ozgune 9y ago
(I'm making an educated guess about the author's intent.) I think the author wanted to keep the example brief and omitted several columns from the todo_lists table. In practice, you may have a creation time, last edit time, share
136.
by ozgune 9y ago
If your comment is related to H1B, I think you may be confusing this visa type with an O1. To apply for an H1B, you don't need to be highly skilled or have expert skills. For the H1B, you only need to be applying to work in a "spe
137.
AWS Launches Redshift Spectrum, which lets users query S3 data(google.com)
2 points by ozgune 9y ago|0 comments
138.
Ask HN: Does AWS EBS have contradictory availability and durability guarantees?
2 points by ozgune 10y ago|2 comments
139.
by ozgune 10y ago
TLDR: This depends on your requirements. We find that users with similar requirements follow one of two approaches: (1) You keep raw data for a certain time period and regularly roll it up: https://www.citusdata.com/blog&#x2
140.
by ozgune 10y ago
(Ozgun from Citus Data) Yup, good point. This example shards the github_events table on user_id and then shows running count(distinct user_id). Since the sharding and count(distinct) column is the same, Citus can push down the count(distinc
141.
by ozgune 10y ago
(Ozgun from Citus Data) Your observations on cstore_fdw are accurate. I'm adding a few points about our learnings from cstore deployments in production. From a use-case standpoint, we find that most cstore deployments use it for data a
142.
by ozgune 10y ago
(Ozgun from Citus) As someone who interacts with PostgreSQL on-prem and cloud deployments frequently, I'm curious on the Hacker News community's thoughts on one question. AWS has a fairly mature RDS Postgres offering. What would m
143.
by ozgune 10y ago
(Ozgun from Citus Data) I think the answer to your question depends on the workload you're planning to use Citus for. We find that users rely on Postgres for different use cases and Citus' benefits (and worst parts :)) vary across
144.
by ozgune 10y ago
Fair point on creating these functions in a Citus schema. The reason for this is mostly historical. We started with pg_catalog, haven't run into issues yet, and therefore didn't prioritize changing this [1]. On the VACUUM table si
145.
by ozgune 10y ago
(Ozgun from Citus) Yup, two good points. When you use this model, Citus guarantees ACI* and T for transactions that are scoped to shards on one machine. It also handles auto-failover. On one big customer being much bigger than the other, tw
146.
Scaling out relational data models, and SQL, through co-location(citusdata.com)
52 points by ozgune 10y ago|16 comments
147.
by ozgune 10y ago
For anyone who's interested, the following paper on load shedding is also a good read: https://pdos.csail.mit.edu/6.828/2010/readings/mogul96usenix... The paper basically identifies the problem as a &quo
148.
by ozgune 10y ago
Compared to the one database per tenant method, this approach scales to more tenants with fewer resources. In particular, you're now asking the database to manage HW/SW resources (cpu, ram, disk, network, and OS resources) for you
149.
by ozgune 10y ago
(Ozgun from Citus Data. I compiled the following from Aurora talks and tutorials I've attended. Happy to edit it with more info.) I don't think you need to worry about tuning things for the planner. Aurora Postgres and Postgres us
150.
by ozgune 10y ago
(From AWS Aurora's website) We’re now previewing the addition of PostgreSQL compatibility to Amazon Aurora. This edition has the benefits customers have come to expect from Aurora, including high durability, high availability, and the

More ›