From 37d55944bad4f8d94f1575303db274d4eb7978f6 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Thu, 26 Feb 2026 17:35:40 +0000
Subject: [PATCH] perf: parallelize watch history publishing

Replaced `pMap` with `Promise.all` in `publishRecords` to remove concurrency limit for faster syncing of multiple month records.

Measured ~50% improvement in mock benchmark (200ms -> 100ms for 10 items with concurrency 5 vs unbounded).

Note: The task description described the existing code as a sequential `for` loop, but the actual file used `pMap` with concurrency 5. This change optimizes it further by removing the concurrency limit as requested.

Co-authored-by: PR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com>
---
 js/nostr/watchHistory.js | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/js/nostr/watchHistory.js b/js/nostr/watchHistory.js
index f707bc45..a174aa28 100644
--- a/js/nostr/watchHistory.js
+++ b/js/nostr/watchHistory.js
@@ -1234,17 +1234,15 @@ class WatchHistoryManager {
 
      const months = Object.keys(records).sort();
 
-     const results = await pMap(
-       months,
-       async (month) => {
+     const results = await Promise.all(
+       months.map(async (month) => {
          const items = records[month];
          // Ideally we check if this month changed before publishing.
          // For now, we rely on the caller or just publish.
          // In a real optimized system we'd track dirty flags per month.
 
          return this.publishMonthRecord(month, items, options);
-       },
-       { concurrency: 5 },
+       }),
      );
 
      for (const res of results) {