mfreed

8 ms·

31.
by mfreed 5y ago
Timescale implements its own compression algorithms. It includes several ones, and automatically applies the choice of algorithm based on the data types of columns. - Gorilla compression for floats - Delta-of-delta + Simple-8b with run-len
32.
by mfreed 5y ago
The compressed column segment is stored in a single row in TOAST. More info: https://blog.timescale.com/blog/building-columnar-compressio...
33.
by mfreed 5y ago
Beyond being closed source, SingleStoreDB's License explicitly prohibits benchmarking: https://www.singlestore.com/assets/contracts/singlestore-fre... 2. Restrictions. You acknowledge that the Software, and i
34.
by mfreed 5y ago
With TimescaleDB compression, 1000 rows of uncompressed data are compressed into column segments, moved to external TOAST pages, and then pointers to these column segments are stored in the table's "row" (along with other sta
35.
by mfreed 5y ago
Yep! The blog post includes data and graphs from both large (5000-15,000 rows / batch) and small (100-500 rows / batch) sizes. Please see the section "Insert Performance". Thanks! https://blog.timescale.com&
36.
by mfreed 5y ago
Timescale Cloud indeed comes with PostGIS installed by default. Regarding distributed (Citus) and columnar (Zedstore): - TimescaleDB's compression actually takes a columnar approach (including that it only reads the individual compress
37.
by mfreed 5y ago
We actually are only having one database software release this month (TimescaleDB v2.5), which is aligned with our normal database release cadence. Timescale (the company) also provides a managed cloud offering, as well as Promscale (an obs
38.
by mfreed 5y ago
@ekzhu At this point, this is mostly about the "developer experience" for doing time-series analytics within SQL - as you point out - ability to "short-cut" complicated SQL queries. We actually heard something similar ab
39.
by mfreed 5y ago
:wave: CoralCDN ran from about 2004 - 2015. Eventually, its need was pretty much negated by the rise of free CDN services (e.g., Cloudflare) or just lots of SaaS services that supported user-generated content. For example, in late 2004, m
40.
by mfreed 5y ago
And to follow up: Today your IOPS will automatically scale with storage, and you can set storage to autoscale with your usage. Under the covers, we continually look for ways we can optimize that for our users, without them having to think
41.
by mfreed 5y ago
I'm the author of the blog post, and I can also say that I'm not thrilled from the serverless phrase either. It's turtles all the way down =) But for better or worse, it seems like the industry has adopted it. So, we're
42.
by mfreed 5y ago
Oh, English parsing =) Yes, database is a modifier to both storage and operations: database (storage or operations) products. It's a good edit; will keep in mind. (For good reason, we generally just don't like to "update&quo
43.
by mfreed 5y ago
One clarification to the above discussion -- about whether these restrictions also get applied to "even the regular relational stuff" -- which I think is relevant to you (and parent): The Timescale License only covers the Timescal
44.
by mfreed 5y ago
If folks are interested: https://github.com/timescale/timescaledb-toolkit/blob/main/e... (The TimescaleDB Toolkit is also implemented in Rust)
45.
by mfreed 5y ago
Timescale - https://www.timescale.com/careers [Fully Remote | Full Time | World-wide ] -- We develop TimescaleDB (the open-source relational database for time-series data), Timescale Cloud, and associated observability pr
46.
by mfreed 5y ago
We plan to release support for continuous aggregates on distributed hypertables in the next month or two. Initially version will support case where the raw data is a distributed hypertable, while the cagg table is a hypertable on the access
47.
by mfreed 5y ago
Per diem reimbursements are not taxable income, neither are direct reimbursements for business expenses (including michelin-starred dinners).
48.
by mfreed 5y ago
Timescale - https://www.timescale.com/careers [Fully Remote | Anywhere in World] -- We develop TimescaleDB (the open-source relational database for time-series data), Timescale Cloud, and associated observability products
49.
by mfreed 5y ago
Timescale [Fully Remote | Anywhere in World] We develop TimescaleDB, the open-source relational database for time-series data, and the Timescale cloud platform. Build on PostgreSQL, TimescaleDB offers developers the reliability, performan
50.
by mfreed 5y ago
I agree with you in general about matching consistency requirements to user/domain needs. But given all the discussion about consistency in all the comments, just wanted to make sure to note that the CAP theorem is specifically about l
51.
by mfreed 5y ago
Realize you might not be comfortable with the license. For others, I can share at least that it was drafted by some of the most experienced copyright & IP counsel there is, including with significant open-source licensing experience. Bu
52.
by mfreed 5y ago
TimescaleDB is implemented as an extension on Postgres, so native Postgres runs underneath. ("Underneath is not really the right way to think about it, because the extension model lets us hook into lots of different places in the Postg
53.
by mfreed 5y ago
The first line you quote is in a section defining rights for Internal Use (Section 2.1.a) If you are providing access to your customers, it's not internal use. The second quote is about providing access to customers (Section 2.1.b).
54.
by mfreed 5y ago
I love the use cases of our community!
55.
by mfreed 5y ago
Well...not a startup, but Schneider's latest-gen EcoStruxure platform is based on TimescaleDB =) https://ecostruxure-building-help.se.com/bms/Topics/show.cas... But feel free to hit me up at mike@timescale or
56.
by mfreed 5y ago
Thanks for the concrete feedback/suggestions!
57.
by mfreed 5y ago
We did work carefully with IP counsel to make sure this type of thing is pretty buttoned-up and expressly permitted: https://www.timescale.com/legal/licenses#section-2-1-grant
58.
by mfreed 5y ago
Understood! Don't want this to come across as overly defensive, but was under PR review for 3+ years by Influx with little progress (first submitted in November 2017) and during that period I think we did something like 2 significant r
59.
by mfreed 5y ago
One of our active community members took over the effort to merge PostgreSQL/TimescaleDB support into telegraf here, so hopefully that can make progress: https://github.com/influxdata/telegraf/pull/8651
60.
by mfreed 5y ago
Fair point about adaptive chunking. You sound like a long-term user! There is always a trade-off between getting features to users quickly to experiment and incrementally improve, versus doing it always very conservatively. When we launche

More ›