hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

9K
active users

#timescale

0 posts0 participants0 posts today

#Ukraine #TimeScale of #RuInvasion

"2014, russian invasion: timescale explained in one minute" [ ± 1min]
by StarskyUA

youtube.com/shorts/VLiNhhayz5o

Quote by SUA:
"2023, May 7
So, putin was courageously protecting people of Donbas who were being slaughtered by the Ukrainian revolutionaries? Explained in one minute."

#SlavaUkraini ! #HeroyamSláva!
#RussiaIsATerroristState

Are there any #PostgreSQL / #Timescale specialists here? I wonder if it is a bad idea to define very long running jobs. Here in particular it's about having a daily job that moves “old” hypertable chunks to another tablespace. Initially this takes a long time (several hours), later it should be faster, as there is not always something to do for all tables.

Class:Chondrichthyes
Subclass:Elasmobranchii
Superorder:Selachimorpha
Order:Lamniformes
Family:Lamnidae
Genus:†Cosmopolitodus

Specie
†Cosmopolitodus hastalis Agassiz, 1843 (broad-toothed mako)

Lived from the Eocene epoch to the Pleistocene epoch

#Cosmopolitodus hastalis is an extinct specie of commonly known as broad-tooth #whitesharks. Fossils are found in the marine strata.

Photo found in facebook
Museo de Historia Naturalis, in Lima, Peru.

If you run a self-hosted instance of Timescale, be sure to monitor jobs:

- timescaledb_information.job* tables
- timescaledb.max_background_workers and max_worker_processes
- ensure background workers are started by running _timescaledb_internal.start_background_workers() (there's a typo in the doc 👀)

docs.timescale.com/self-hosted
docs.timescale.com/use-timesca

The compression and retention jobs were not running on our instances, filling up disk 🚀

docs.timescale.comTimescale Documentation | TimescaleDB configuration and tuningHow to change configuration settings for TimescaleDB

Goodness we love the #grafana pipeline.
You start off introducing it in a small project at work.
Next thing you know a colleague asks if you can help set it up for their item, then a few weeks later the Section Leader of your group asks if you can get it running for some of their systems.

As of now, we are having a trial run of monitoring all 1000+ Dipole Magnets of the #CERN #LHC, using #grafana, #timescale and some #Python running the #dataacquisition

#Observability for the win!

Continued thread

And after adding in the complete set of all #Cern #lhc Power Lead temperature sensors, the graph now looks far more stellar!

With 220 sensors providing data we are helping keep the accelerator's #superconductor magnets safely powered - and the data it generates looks absolutely fantastic as well

This graph here no longer shows a plot per individual sensor, but rather a heatmap of all sensors - beautifully visualising the operational heartbeat with #timescale and #grafana for plots <3

The heartbeat of a machine can be seen in many locations - in this case, in the monitoring of temperatures inside the #cern #lhc magnet power connectors using #grafana and #timescale

These connectors interface between the outside world and the cosmically cold cryogenics of the superconductor inside. If not monitored and heated, they can freeze and form ice and dew!
As the machine ramps power up and down, so do their temperatures, forming an imprint of the daily operations in the graphs.

After two weeks of brainstorming, we have finally migrated:

- 7 databases
- with hypertables
- used by
- 1.8TiB
- 5 minutes of downtime

Some databases didn't have hypertables on the source but we needed them on destination.

The workload is now manageable for those databases 🎉

Don't forget to enable and configure Timescale from day 1 if you setup Zabbix running on PostgreSQL. That will be way easier than doing afterwards 👍🏻

zabbix.com/documentation/curre

www.zabbix.com5 TimescaleDB setup

We may once again be tasked with scraping/polling data off of a slow scientific "big data" database and into #Timescale for a smoother live plotting experience in #Grafana

You'd think CERN would use a dedicated time series store for monitoring data but no, its HDFS+Spark??

The kind of system that, when you ask people about, will say "Oh no I've managed to avoid worrying about it until now" and "It works if you're patient".

We'll give them a taste of sub-second query times~

Recently, we have discovered that some databases running on were maxing i/o capacity.

We have found out that the housekeeping job, responsible of removing old metrics, was responsible of thousand of DELETE queries. Enabling and configuring (via Zabbix config) drastically reduced the pressure.

How? By dropping chunks (partitions) instead of deleting rows one by one.

zabbix.com/documentation/curre

Slighlty disappointing to see #Influxdb 3's release saying it's "45x faster than Open Source" (referring to the Influx OSS version), and moving to a fully cloud-hosted system... And yet another rewrite, of course.

#timescale's TSL license feels more sensible, keeping the code open source and usable. We think they found a sustainable middle ground for their software, especially compared to what Influx just did.

Specious Timescales from Sedimentary Layers
Changing environments can dramatically change how quickly layers form in sedimentary rocks, leading to incorrect time estimates.
New research shows that environmental conditions can substantially affect how—and how fast—sediment accumulates, misleading scientists who are trying to estimate the lengths of time periods in Earth’s past.
eos.org/research-spotlights/sp #sedimentary #layers #geohistory #timescale

EosSpecious Timescales from Sedimentary LayersBy Saima May Sidik