Systems research · Resource optimization
The systems problems I enjoy most begin after something works: can it use fewer resources, stay responsive under pressure, and degrade gracefully when resources run out?
Currently, I study Linux memory pressure through PSI, swap, compressed memory, cgroup isolation, and controlled responsiveness experiments.
Broader goal
How can memory-management policy preserve responsiveness when RAM is constrained?
Evidence to date
Controlled reruns show PSI before material swap growth under the tested memory-pressure workloads. A corrected, phase-aligned responsiveness canary now records pressure-related response and service-time degradation, while compression-sensitivity runs distinguish structured from random page content.
Baseline signal validation and compression-sensitivity work are complete. The cgroup-scoped sustained-PSI guided-zram comparison is underway. The current evidence does not establish that guided zram improves responsiveness or outperforms static swap backends; that is the purpose of the active policy screen.
Earlier work in Nepali legal information retrieval, embedding evaluation, and AI-assisted research workflows.
An empirical study of embedding choices for retrieving Nepali legal documents in a low-resource setting.
Study contribution: Compares retrieval behavior rather than treating embedding choice as an implementation detail, with attention to the constraints of Nepali legal text.
A lightweight pipeline that generates search terms, retrieves open-access papers, ranks them with transformer embeddings, and applies statistical thresholding.
Study contribution: Evaluates three embedding models and documents a practical preliminary-review workflow without claiming ground-truth relevance labels that were not collected.
A retrieval-augmented legal analysis pipeline designed for access to information in the Nepalese legal context.
Study contribution: Processes legal documents for retrieval, expands user queries, and evaluates rule-recall, rhetorical-understanding, and interpretation-oriented questions.
Selected Rust systems projects involving execution state, persistence, workspace restoration, and terminal interfaces.
A Rust notebook interface for exploratory Python work, using a human-editable Markdown format with Jupyter import/export and checkpointed runtime state.
Systems focus: Execution state, notebook serialization, kernel management, environment selection, and terminal interaction.
A Rust terminal multiplexer centered on declarative project layouts, persistent sessions, and best-effort workspace restoration. It grew from an earlier tmux session helper, Smart Session Manager.
Systems focus: PTY management, session persistence, and the boundary between shareable project configuration and machine-local runtime state.
Selected experiment logs, methodology notes, and reading notes from ongoing systems work.
What PSI/swap validation established, why responsiveness measurement changed, and what the active guided-zram screen can still prove.
Docker packages layered filesystems with metadata and uses Linux namespaces, cgroups, and the shared host kernel to run isolated, reproducible environments without full virtual machines.