For ADHD in particular, I've tried Adderall/Vivance, Ritalin/Concerta, Atomextetin and couple of others whose name I forgot.
Based on the suggestions of the report I have started taking Guanfacine/Intuniv.
For ADHD in particular, I've tried Adderall/Vivance, Ritalin/Concerta, Atomextetin and couple of others whose name I forgot.
Based on the suggestions of the report I have started taking Guanfacine/Intuniv.
By the gods! Why didn't I think about that!? 🤦♂️
Thank you!
root directory
Where your settings, bookmarks, passwords, etc are stored.
local directory
Where your cookies, website local storage and other temporary non-profile data is stored.
could not resize shared memory
That means too many chunky parallel maintenance workers are using the memory at the same time (max_parallel_maintenance_workers
and maintenance_work_mem
.)
VACCUM
ing is a very important part of how PG works; can you try setting max_parallel_maintenance_workers
to 1 or even 0 (disable parallel altogether) and retry the experiment?
I did increase shared_buffers and effective_cache_size with no effect.
That probably rules out the theory of thrashed indices.
https://ctxt.io/2/AABQciw3FA https://ctxt.io/2/AABQTprTEg https://ctxt.io/2/AABQKqOaEg
Since those stats are cumulative, it's hard to tell anything w/o knowing when was the SELECT
run. It'd be very helpful if you could run those queries a few times w/ 1min interval and share the output.
I did install Prometheus with PG exporter and Grafana...Anything specific you can suggest that I should focus on?
I'd start w/ the 3 tables I mentioned in the previous point and try to find anomalies esp under different workloads. The rest, I'm afraid, is going to be a bit of an investigation and detective work.
If you like, you can give me access to the Grafana dashboard so I can take a look and we can take it from there. It's going to be totally free of charge of course as I am quite interested in your problem: it's both a challenge for me and helping a fellow Lemmy user. The only thing I ask is that we report back the results and solution here so that others can benefit from the work.
I used to be in a relatively similar position years ago so I totally relate to what you've got to do on a daily basis.
These are the the titles that come to my mind (leaving ths seniority level up to you):
"Do you not know my son, with how little wisdom the world is governed?" 🤷♂️
Oh, updated the link 🤦♂️
The stock Grafana dashboard for PG is a good starting point. At least, that's how I started. You really should add new metrics to your dashboard if you really need them as you said.
Don't forget to install node-exporter too. It gives some important bits of info about the PG host. Again the stock dashboard is a decent one to start w/.
Extensions either save their settings in the "cloud" or locally.
If you've got Firefox Sync setup, the ones which write to "cloud" will be automatically backed up for you.
Some extensions also offer to export your config to a file so that you can import it later.
It all varies by extension and impossible to tell w/o knowing which ones you're using.
That said, you can always safely experiment using a new profile w/o needing to delete the current one. Create a new profile (launch firefox using firefox -P
) and see if copy-paste works properly in there. If yes, then you can add your extensions one by one to the new profile w/o losing your settings.
I've never had this problem so can't tell for sure. But have you tried the solution in the very link you shared?
Also had copy/paste not working on some sites. Noticed that dom.event.clipboardevents.enabled was set to false. Set it to true on about:config page, now everything works.
A few things off the top of my head in order of importance:
How frequently do you VACCUM
the database? Have you tried VACCUM
ing a few of times over a 5 min span & see if there are changes to the disk I/O aftewards?
I've got no idea how Lemmy works but "seeding content", to my mind, possibly means a lot of INSERT
/UPDATE
s. Is that correct? If yes, there's a chance you may be thrashing your indices & invalidating them too frequently which triggers a lot of rebuilding which could swallow a very large portion of the shared_buffers
. To rule that out, you can simply bump shared_buffers
(eg 16GB) & effective_cache_size
and see if it makes any difference.
Please include a bit more information about PG activity, namely from pg_stat_activity
, pg_stat_bgwriter
& pg_stat_wal
.
You've got quite a high value for max_connections
- I don't believe that' s the culprit here.
And finally, if possible, I'd highly recommend that you take a few minutes & install Prometheus, Prometheus node exporter, Proemetheus PG exporter and Grafana to monitor the state of your deployment. It's way easier to find correlations between data points using the said toolset.
I missed the point wrt 2021. That's somehow comforting/reassuring. Thanks.
Oh and it cost me around $600 which is not covered by insuranoe.