Skip to content

Bug - Content entities - Navigation and search fail (or run extremely slowly) on large datasets #1219

Closed

Description

@kodster28

Description

When you have a large set of content entities, the navigation and search of those content entities doesn't work as expected.

Navigation

For navigation, large sets of content entities seem to hit some API limits (or latency) and take a long time to query -- in my testing around 20 seconds or more to load a new panel if you're trying to go back pretty far.

Screen.Recording.2026-05-29.at.3.27.26.PM.mov

Search

A similar problem happens when you're trying to search for a content entity that lives further back in the collection.

From the initial page, it isn't included in the index

Image

It's only once you navigate to that page directly (or at least near it, haven't tested fully), that the entity item will be truly searchable.

Steps to reproduce

  1. Create a content entity.
  2. Add a lot of entries. Over 1000.
  3. Try searching or navigating those entries.

Environment

  • emdash: 0.15.0
  • Cloudflare Workers
  • MacOS, Chrome

Logs / error output

Activity

  1. added a commit that references this issue on Jun 2, 2026
    9422d6a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions