vmtouch VS lnav

VMTouch may be helpful. https://hoytech.com/vmtouch/

Just lock the file into memory using:

```vmtouch -l /path/to/binary```

You're claiming that gnome loads all of itself into memory so that it can be faster. Now there are a few reasons why I don't think that's a reasonable idea, but assuming that you wanted that... using techniques like vmtouch to keep the files in the disk cache would make it so that gnome wasn't actually using the full 1GB. The "cached" files could be evicted from the cache if some other program needed that memory. Where as loading all of gnome in at startup regardless of whether it's actually used is probably not a good idea.

It is a mainstream thing. It's enabled by default on every Windows install, as far as I know, although you may not be impressed by its understanding of what your frequently opened programs are. It's been about ten years since I ran Windows, but I used to have a batch script to read everything in a directory so that it would be in the disk cache and subsequent accesses would come from RAM. The Linux equivalent of my script is vmtouch, although that's a lot more full-featured.

vmtouch: https://hoytech.com/vmtouch/

vmtouch.

See https://lnav.org for a powerful mini-ETL CLI power tool; it embeds SQLite, supports ~every format, has great UX and easily handles a few million rows at a time.

The code base seems like a good reference as a small Python project.

My fav option in this class of apps: https://lnav.org/ It lets you use journalctl with pipes as requested here: https://github.com/Textualize/toolong/issues/4

For local development, I cannot recommend lnav[1] enough. Discovering this tool was a game changer in my day to day life. Adding comments, filtering in/out, prettify and analyse distribution is hard to live without now.

I don't think a browser tool would fit in my workflow. I need to pipe the output to the tool.

[1] https://lnav.org/

It looks like they run an SSH server inside a Docker container defined by this Dockerfile [1]. This uses the ForceCommand directive in the sshd_config file to ensure that a specific command is run when a user connects (rather than the user connecting directly to a shell).

Depending on whether the user connects as the `playground` or `tutorial1` user they interact with a bash script that is either [2] or [3].

[1]: https://github.com/tstack/lnav/blob/master/demo/Dockerfile

[2]: https://github.com/tstack/lnav/blob/master/docs/tutorials/pl...

[3]: https://github.com/tstack/lnav/blob/master/docs/tutorials/tu...