![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
Assuming one hears their own voice in recorded form enough times, that “strange” feeling it might give at first subsides.
Assuming one hears their own voice in recorded form enough times, that “strange” feeling it might give at first subsides.
You didn’t mention how big those volumes are and how frequently the data changes.
Assuming it’s not that much data:
tar
to archive each volume first, while using proper options to preserve permissions and whatever else is important for your usecaserestic
, but maybe you can backup those archives separately and apply a more aggressive pruning strategy just for them20 mph (32 km/h) on a regular bike is doable, but yeah, usually that involves a very “flat” road or even a road that has a slight decline. And as you’ve said, maintaining it (e.g. for more than 10 seconds) is a whole different story.
Furthermore, it also requires a certain fitness level and “bodily involvement”. The thing that still catches me off guard at times is how relaxed some people on ebikes look while going that fast. Whatever kind of judgement I could make in the past on how fast someone is approaching based on how much they “visually excert themselves” (e.g. hunching forward or even standing up) kind of has become meaningless with ebikes.
‘Tasks’ (open source android app) can do this. Likely you already knew (others likely don’t). But I agree, a surprisingly uncommen feature.
I went through setting up netdata for a sraging (in progression for a production) server not too long ago.
The netdata docs were quite clear on that fact that the default configuration is a “showcase configuration”, not a “production ready configuration”!
It’s really meant to show off all features to new users, who then can pick what they actually want. Great thing about disabling unimportant things is that one gets a lot more “history” for the same amount of storage need, cause there are simply less data points to track. Similar with adjusting the rate which it takes data points. For instance, going down from default 1s internal to 2s basically halfs the CPU requirement, even more so if one also disables the machine learning stuff.
The one thing I have to admit though is that “optimizing netdata configs” really isn’t that quickly done. There’s just a lot of stuff it provides, lots of docs reading to be done until one roughly gets a feel for configuring it (i.e. knowing what all could be disabled and how much of a difference it actually makes). Of course, there’s always a potential need for optimizations later on when one sees the actual server load in prod.