It's on π₯³
If you've got questions/feedback/ideas please drop a line in either
Thanks for showing interest π
Latency, aka Roundtrip Time (RTT) or Time To Load (TTL), is the time it takes for the instance to respond to an HTTP request.
Latency indicators have been added to the instance health breakdown dashboard, allowing you to view the latency of your favourite instance compared to itself:
- Past 3 hours compared to the past 7 days
- Past 24 hours compared to the past 30 days
- Past 24 hours compared to the past 90 days
Screenshot 1
Screenshot 2
As of a couple of days ago, uptime indicators have been added to the health breakdown page allowing you to glance at the availability of the instance during the past 7, 30 and 90 days.
Screenshot 1
Screenshot 2
Update
sh.itjust.works in now added to lemmy-meter π₯³ Thanks all.
I didn't like the capitalised names so configured xdg to use all lowercase letters. That's why ~/opt fits in pretty nicely.
You've got a point re ~/.local/opt but I personally like the idea of having the important bits right in my home dir. Here's my layout (which I'm quite used to now after all these years):
$ ls ~
bin
desktop
doc
downloads
mnt
music
opt
pictures
public
src
templates
tmp
videos
workspace
where
binis just a bunch of symlinks to frequently used apps fromoptsrcis where i keep clones of repos (but I don't do work insrc)workspaceis a where I do my work on git worktrees (based offsrc)
Thanks! So much for my reading skills/attention span π
Which Debian version is it based on?
Something that I'll definitely keep an eye on. Thanks for sharing!
RE Go: Others have already mentioned the right way, thought I'd personally prefer ~/opt/go over what was suggested.
RE Perl: To instruct Perl to install to another directory, for example to ~/opt/perl5, put the following lines somewhere in your bash init files.
export PERL5LIB="$HOME/opt/perl5/lib/perl5${PERL5LIB:+:${PERL5LIB}}"
export PERL_LOCAL_LIB_ROOT="$HOME/opt/perl5${PERL_LOCAL_LIB_ROOT:+:${PERL_LOCAL_LIB_ROOT}}"
export PERL_MB_OPT="--install_base \"$HOME/opt/perl5\""
export PERL_MM_OPT="INSTALL_BASE=$HOME/opt/perl5"
export PATH="$HOME/opt/perl5/bin${PATH:+:${PATH}}"
Though you need to re-install the Perl packages you had previously installed.
NB: I have never had the fortune to write Lisp in a professional setup.
For years, I used to use SBCL snippets for a whole set of automation tasks in my daily workflow, like updating git repos in batch, checking failing CI/CD pipelines per repo, organising my music collection, etc.
But gradually I switched to more specialised tools and, yes, Emacs Lisp to do what I needed to do. It just felt more ergonomic in my case.
The last time I seriously used SBCL was to solve some of Project Euler's challenges back in 2018: https://github.com/bahmanm/euler-cl
Nowadays, I've got no non-elisp code left π π€·ββοΈ
First off, I was ready to close the tab at the slightest suggestion of using Velocity as a metric. That didn't happen π
I like the idea that metrics should be contained and sustainable. Though I don't agree w/ the suggested metrics.
In general, it seems they are all designed around the process and not the product. In particular, there's no mention of the "value unlocked" in each sprint: it's an important one for an Agile team as it holds Product accountable to understanding of what is the $$$ value of the team's effort.
The suggested set, to my mind, is formed around the idea of a feature factory line and its efficiency (assuming it is measurable.) It leaves out the "meaning" of what the team achieve w/ that efficiency.
My 2 cents.
Good read nonetheless π Got me thinking about this intriguing topic after a few years.
This is fantastic! π
I use Perl one-liners for record and text processing a lot and this will be definitely something I will keep coming back to - I've already learned a trick from "Context Matching" (9) π
Update 1
Thanks all for your feedback π I think everybody made a valid point that the OOTB configuration of 33 requests/min was quite useless and we can do better than that.
I reconfigured timeouts and probes and tuned it down to 4 HTTP GET requests/minute out of the box - see the configuration for details.
π A pre-release version is available at lemmy-meter.info.
For the moment, it only probes the test instances
- enterprise.lemmy.ml
- ds9.lemmy.ml
- voyager.lemmy.ml
I'd very much appreciate your further thoughts and feedback.
Oh, sorry to hear that π
I think I'll just go ahead and add you folks to lemmy-meter for now. In case you want to be removed, it should take only a few minutes.
I'll keep this thread posted once things are done.