camber-weaverB
Via another reddit thread on the topic, I found this YouTube playlist which has been super helpful. Just re-posting it here for posterity:
https://www.youtube.com/playlist?list=PLbNp7AIu8VYyzsocLUdCScF4zvou8rzS9
Thanks, y’all.
I don’t think I need so many drives so now its just a matter of verifying that if I scoop one or two low-RAM-specs off of eBay for cheap I will be able to re-populate them with RAM.
This is pretty interesting…
It appear as though your workflow is pretty similar to mine when producing technical documentation. I need to dig into this a bit. Hope you don’t mind me asking a question after only having done a quick fly-by…
What is the ob type ‘compile’? I’ve never seen that one. Something you’ve created or something that has just been under my radar?
I’ve noticed I have a lot of latency right after startup and the thing which seems to help is a manual garbage collect. That’s bit odd because the last thing I do in my config is set a 5 second timer which is fed a lambda to run a gc after the timer expires. Regardless, I still have better results if I run the gc manually.
I do load of metric ass ton of packages (and modes) and I recursively parse my Org/Org Roam directory for org-agenda items so I’m doing a lot of questionable things.
As others have said, sounds like we might both benefit by spending some quality time with the profiler.
This is pretty much exactly what I do. The only real hiccups I can think of:
-
If you use Org Roam the different machines will have their own Sqlite databases and thus you may need to do an org-roam-db-sync when hopping.
-
org-agenda may need to be refreshed when hopping machines.
I have bound keys for both of those things to make the manual portion as non-disruptive as possible.