Skip to content

@ccusage/codex: It's really slow and uses 30GB of memory #885

Closed

Description

@doublemover

I think it should be effectively instant (it takes several minutes on a very fast machine), especially on re-runs, and also not use that much memory. I don't think I've used an obscene amount or anything, maybe 100B tokens.

Thank you

Activity

  1. AshyEarl commented on Mar 17, 2026

    @AshyEarl
  2. doublemover commented on Mar 17, 2026

    @doublemover
    Author

    Please dont shit up issues with spam. It's also wrong btw

  3. AshyEarl commented on Mar 22, 2026

    @AshyEarl

    Please dont shit up issues with spam. It's also wrong btw

    Sorry, I shouldn't have posted this here. I just ran into the same issue myself and wrote a small tool hoping to help others with similar problems. My apologies.

  4. ryoppippi commented on May 17, 2026

    @ryoppippi
    Member

    The current Codex adapter no longer uses the old @ccusage/codex whole-file loading path. It scans JSONL by markers and uses worker-based parsing so only relevant token_count lines are processed. The streaming work from the #953/#952 area is also present, so the tens-of-GB memory problem reported here is resolved on current main. Further Codex performance improvements should be tracked in #877 and #922.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions