Skip to content
This repository was archived by the owner on Jun 30, 2026. It is now read-only.
This repository was archived by the owner on Jun 30, 2026. It is now read-only.

explore feels slow in big tables聽#26

Open

Description

@amtoine

i think the TUI renders every row of the data, even if it's out of the screen 馃

this means that a table with 15000 rows will feel much slower than the first 100 lines of the same table.

Activity

  1. amtoine commented on Sep 4, 2023

    @amtoine
    OwnerAuthor

    if the history is big enough, one can compare

    open $nu.history-path | query db "SELECT * from history" | first 20000 | explore

    and

    open $nu.history-path | query db "SELECT * from history" | first 200 | explore

    alternately, one can use the following command to generate a dummy table of a certain length

    def t [n: int] {
        let ids = seq 1 $n | each { random uuid } | wrap id
        let names = seq 1 $n | each { random chars --length 64 } | wrap name
        let vals = seq 1 $n | each { random int } | wrap val
    
        $ids | merge $names | merge $vals
    }

    it starts to feel slightly slow with t 10_000, and it gets worse with t 20_000 and t 30_000 freezes.

    Note

    also works with seq 1 $n with $n = 10^{5}$

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions