PaulWaldman
Joined 15 years ago
Joined 15 years ago
https://newsroom.porsche.com/en/press-kits/taycan/Die-Driver...
> InfluxDB 3 Core gives developers a new tool for time series data management—a high-performance recent-data engine optimized for querying the last 72 hours of data. This focused approach enables Core to deliver exceptional performance for real-time monitoring, data collection, and streaming analytics use cases. By optimizing specifically for this pattern, we’ve achieved query response times under 10ms for last-value queries and under 50ms for hour-long ranges.
The limitation of 72 hours of data is a bit disappointing. There are use cases that don't require 50ms query response times, but instead need longer on-prem storge. InfluxDB 1.X and 2.X supported these well. Would it be possible to reduce query performance and extend data retention?
Is there any guidance on a planned EOL for InfluxDB 1.X and 2.X once Core reaches GR?
Are all government contractors required to provide the source code for all developed applications? Or does this bill only apply to contracts where the deliverables actually include source code?
Many web properties are no longer accessible due to M&A activity and Small/solo publishers unable or unwilling to maintain their assets. Archives like WayBack Machine mitigates some of the loss of digital content so long as the archives themselves are still maintained.
Will spinning rust be as durable as Microfiche?
I don't know, how often would you stop at a gas station if their pumps weren't reliable? Many 3rd party chargers are selling electricity at a mark-up.