Skip to content

Commit 114d60c

Browse files
christiangdaclaude
andcommitted
docs: add performance improvements to What's New v0.44.0
Document concurrent user fetching, optimized member comparison, and goroutine leak safety with synctest. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent a0b27b6 commit 114d60c

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

docs/Whats-New.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,3 +21,11 @@ Fixed a bug where group members were re-synced on every Lambda execution even wh
2121
**Root cause:** `MergeGroupsMembersResult` was not consolidating entries for the same group when merging "created" and "equal" member sets. This produced duplicate group entries in the state file, causing the groups-members hash to never match the IDP data on subsequent syncs.
2222

2323
**Impact:** After upgrading, the first sync will reconcile the state file automatically. Subsequent syncs will correctly skip member reconciliation when no changes are detected.
24+
25+
### Performance Improvements
26+
27+
* **Concurrent user fetching:** `GetUsersByGroupsMembers` now fetches user details from the Google Workspace API concurrently (up to 10 parallel requests) instead of sequentially. For deployments with 100+ users, this reduces the user retrieval phase from minutes to seconds.
28+
29+
* **Optimized member comparison:** Removed a redundant O(m) inner loop in `membersDataSets` that iterated over the entire SCIM member set to find an email already confirmed by a direct map lookup. Benchmarks show ~16-19% improvement for large groups.
30+
31+
* **Goroutine leak safety:** Concurrent operations are verified with `synctest.Test` (Go 1.26) to ensure no goroutine leaks in both success and error paths.

0 commit comments

Comments
 (0)