Add a JSONL implementation with benchmark and findings

[cte]

Context

TODO:

• Migrate from old to new file format

I was surprised at how well the pure JSON approach works for huge conversation histories. In short, there are definitely real wins with JSONL, but I'm not sure it matters in practice. I also tried YAML but the JSON parser is way faster natively.

Here's what Roo Code came up with:

Recommendation

Strongly recommend adopting the JSONL implementation for task message storage for the following reasons:

1. Superior Performance: Significantly faster, especially for sequential operations that mirror real-world usage patterns (6.56x speedup)

2. Better Scaling: Performance remains consistent regardless of conversation size

3. Lower Memory Footprint: Only needs to process the new message, not the entire conversation history

4. Append-Optimized: Perfectly suited for chat applications where new messages are frequently added

5. Streaming Compatibility: Easier to implement streaming reads for large conversation histories

The performance advantage of JSONL becomes increasingly significant as conversations grow larger, making it the clear choice for a chat-based application like Roo Code.

Implementation

Screenshots

before	after

How to Test

Get in Touch

---

Important

Add JSONL implementation for task message storage with improved performance and adjust cache settings.

• JSONL Implementation:
  • Adds readTaskMessages, writeTaskMessages, and appendTaskMessage functions in taskMessages.jsonl.ts for handling task messages in JSONL format.
  • Utilizes readline for efficient line-by-line reading and fs for file operations.
• Performance:
  • JSONL format offers superior performance, better scaling, lower memory usage, and is append-optimized.
• Misc:
  • Adjusts taskSizeCache TTL to 30 seconds and check period to 5 minutes in taskMetadata.ts.

^{This description was created by for fc9d4f5. You can customize this summary. It will automatically update as commits are pushed.}

[changeset-bot]

🦋 Changeset detected

Latest commit: fc9d4f5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
roo-cline	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[ellipsis-dev]

The changes in this pull request are cohesive and related to implementing and benchmarking a JSONL format for task message storage. Therefore, it does not need to be split into smaller pull requests. The benchmark results, script, and storage utilities are all part of this implementation and should remain together.

[samhvw8]

can't wait to see this merged 💪🏻

[mrubens]

Do you think jsonl is less likely to get corrupted if the process is force closed or dies?

[cte]

Yes - that's definitely a benefit.

[cte]

I swapped these original; the TTL should be 30s and the check period doesn't really matter.

[sachasayan]

Any blockers here?

[cte]

Any blockers here?

Current blocker is a migration function to convert the old format to the new format, similar to this: https://github.com/RooVetGit/Roo-Code/blob/main/src/core/task-persistence/apiMessages.ts#L26

[hannesrudolph]

stale