# Improving performance of node-find et. al

**URL:** <https://org-roam.discourse.group/t/improving-performance-of-node-find-et-al/3326>\
**Category:** Development\
**Created:** [December 21, 2023, 10:41am UTC](https://org-roam.discourse.group/t/improving-performance-of-node-find-et-al/3326 "2023-12-21T10:41:34Z")\
**Posts on this page:** 1\
**Showing post:** 33

<div class="post-metadata">

**Author:** ![dmg](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@dmg](https://org-roam.discourse.group/u/dmg)\
**Post date:** [July 28, 2024, 5:06pm UTC](https://org-roam.discourse.group/t/improving-performance-of-node-find-et-al/3326/33 "2024-07-28T17:06:24Z")

</div>

I encourage you to try this minor mode:

> **[GitHub - dmgerman/org-roam-gt: Faster finding of nodes and better templates](https://github.com/dmgerman/org-roam-gt)**
>
> Faster finding of nodes and better templates

Enable with org-roam-gt-mode-enable  
and disable with org-roam-gt-mode-disable

This is the result of discussions with @akashp

1. It optimizes the creation of the nodes (the original constructor is very slow)
2. It replaces the code to format the node given the template. I gives the option of replacing the processing of the template (which is currently very expensive) with a call to a function.

The overall result is that, a typical database (say 1-2 k nodes) it feels instantaneous.

The best part is that there is no caching to worry about.

I plan to extend this minor mode with my improved template processing for org-roam (more in line with org templates).

I have been using it for more than 1 month and it seems stable. Since it does not modify the database, there is no risk to those using it (simply disable the minor mode if you don’t like it)

---

_[View the full topic](https://org-roam.discourse.group/t/improving-performance-of-node-find-et-al/3326)._