[Repo Assist] perf: replace List.Insert(0) with LinkedList.AddFirst in NotificationHistoryService#143
Draft
github-actions[bot] wants to merge 1 commit intomasterfrom
Conversation
…HistoryService AddNotification previously called List<T>.Insert(0, ...) which is O(n) due to array element shifting, followed by RemoveAt(_history.Count - 1) to enforce MaxHistory. While RemoveAt on the last element is O(1), the Insert(0) itself degrades to O(n) as history grows. Mirrors the same fix applied to ActivityStreamService in commit bd0a7b0. Change: - List<NotificationHistoryItem> → LinkedList<NotificationHistoryItem> - Insert(0, ...) → AddFirst(...) [O(1)] - RemoveAt(Count - 1) → RemoveLast() [O(1)] - GetHistory() ToList() snapshot is unaffected (IEnumerable<T> is sufficient) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
14 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 This PR was created by Repo Assist, an automated AI assistant.
Summary
NotificationHistoryService.AddNotificationusedList(T).Insert(0, ...)to prepend items, which is O(n) — the entire backing array must shift one position for every insertion. This is the same pattern fixed inActivityStreamServicein commitbd0a7b0(PR #137).Root Cause
Both
Insert(0, ...)and (for a full list) the trim loop together cost O(n) per notification. With a MaxHistory of 100, this is minor but unnecessary — and the pattern is easy to fix uniformly across the codebase.Fix
Replace
List(NotificationHistoryItem)withLinkedList(NotificationHistoryItem):AddFirstandRemoveLastare both O(1) onLinkedList(T). TheGetHistory()snapshot via.ToList()(called on read, not write) is unchanged in complexity.Trade-offs
LinkedList(T)has higher per-node overhead thanList(T)(each node is an object). For a 100-item cap this is negligible (~6.4 KB total vs ~3.2 KB for a List).GetHistory()still returns aList(T)snapshot, so callers are unaffected.Test Status
OpenClaw.Shared.TestsOpenClaw.Tray.TestsNo production logic was changed — only the collection type and its operation methods.