2025-06-26T16:58:31Z

[RESOLVED] Sense Atlas can sometimes be unusably slow.

Dorian Taylor

Even ordinary page GETs when the graph state has not changed can be slow, particularly the first time a user loads a generated resource.

Most (if not all?) of the changes that cause full-page round trips could be supplanted by AJAX (or whatever it's called these days).

Sense Atlas Front End

Sense Atlas is particularly slow after POSTs because the RDF store only has a single global modification time (that I had to hack in).

The edge-uncrossing algorithm in d3-dag (and Sugiyama in general) is known to run superlinearly (how bad?) to the edges it has to uncross.

The effort it takes to map out a set of related issues should be roughly equivalent to composing a thread on Twitter (or descendant), where each entity is analogous to a tweet.

The front-end template is almost certainly doing way more work than it needs to.

The two most robust solutions for speeding up Sense Atlas (plus the visualization layout) are also each fairly significant subprojects.