[jtfmumm]

No description provided.

[github-actions]

Benchmarks: Patchwork with this PR against main

a5938a4 against main at 14a88bd, Patchwork as it ships (patchwork mode), in chromium, firefox and webkit, each on its own runner with main and the PR measured one after the other (run). Lower is better throughout. A row is in the table when every run of the PR came out on the same side of every run of main, with the medians more than 20% apart; every benchmark is below it.

Nothing changed by more than the runs vary.

every benchmark: the median of 3 runs of main and 3 runs of the PR, their range in brackets

browser	benchmark	main	PR	change
chromium	boot → repo, first tab (1 tabs)	206 ms (189–220)	215 ms (204–220)	+5%
chromium	boot → server connected, first tab (1 tabs)	460 ms (428–482)	461 ms (452–469)	+0%
chromium	renderer memory, all tabs + workers (1 tabs)	361 MB (355–362)	357 MB (351–360)	−1%
chromium	renderer processes (1 tabs)	3	3
chromium	boot → repo, first tab (3 tabs)	208 ms (198–225)	223 ms (208–224)	+7%
chromium	boot → repo, last tab (3 tabs)	154 ms (145–162)	150 ms (147–160)	−2%
chromium	boot → server connected, first tab (3 tabs)	471 ms (467–494)	494 ms (479–514)	+5%
chromium	renderer memory, all tabs + workers (3 tabs)	713 MB (703–714)	707 MB (707–714)	−1%
chromium	renderer processes (3 tabs)	5	5
chromium	boot → repo, first tab (10 tabs)	207 ms (196–227)	210 ms (207–211)	+2%
chromium	boot → repo, last tab (10 tabs)	170 ms (143–177)	156 ms (146–157)	−8%
chromium	boot → server connected, first tab (10 tabs)	456 ms (452–489)	469 ms (464–470)	+3%
chromium	renderer memory, all tabs + workers (10 tabs)	1915 MB (1888–1916)	1899 MB (1899–1906)	−1%
chromium	renderer processes (10 tabs)	12	12
chromium	sync still works after the first tab closes	ok	ok
chromium	edit → seen + confirmed, after first tab closed	155 ms (155–159)	159 ms (157–169)	+3%
chromium	server link seen down while offline	ok	ok
chromium	…and the server did not see the offline edits	ok	ok
chromium	tabs converged while offline, over a local channel	ok	ok
chromium	offline edits in two tabs both survive reconnect	ok	ok
chromium	reconnect → tabs converged (only where they hadn't already)	–	–
chromium	…and a fresh tab sees both	ok	ok
chromium	boot → doc open, tab 1	589 ms (585–599)	563 ms (560–571)	−4%
chromium	boot → doc open, tab 2	257 ms (248–274)	253 ms (245–257)	−2%
chromium	boot → doc open, tab 10	227 ms (224–228)	234 ms (223–238)	+3%
chromium	open 40 tabs, wall clock	7341 ms (7323–7417)	7141 ms (7065–7485)	−3%
chromium	boot → repo, last of 40 tabs	47 ms (47–49)	53 ms (52–54)	+14%
chromium	boot → linked, last of 40 tabs	–	–
chromium	boot → server connected, last of 40 tabs	802 ms (732–825)	1066 ms (674–1069)	+33%
chromium	renderer memory, 40 tabs	7470 MB (7423–7502)	7431 MB (7427–7511)	−1%
chromium	renderer processes, 40 tabs	42	42
chromium	39 tabs find the doc: median	555 ms (539–565)	541 ms (484–564)	−2%
chromium	39 tabs find the doc: slowest	623 ms (605–634)	621 ms (620–632)	−0%
chromium	…all 39 found it	ok	ok
chromium	…finds that needed a retry (of 39)	0	0
chromium	edit → seen in 39 tabs: median tab	41 ms (34–43)	36 ms (34–39)	−14%
chromium	edit → seen in 39 tabs: slowest tab	100 ms (97–113)	88 ms (81–96)	−11%
chromium	…tabs that saw every edit (of 39)	39	39
chromium	edit → server holds our heads (40 tabs)	152 ms (149–161)	147 ms (140–155)	−3%
chromium	…server confirmed every edit (40 tabs)	ok	ok
chromium	…longest main-thread stall in tab 0 during the edits	18 ms (13–30)	25 ms (24–26)	+35%
chromium	sync rounds per sibling edit, non-editing tab	0	0
chromium	server bytes received per edit per tab	–	–
chromium	storage writes (saveBatch) per edit per tab	–	–
chromium	worker errors (40 tabs)	–	–
chromium	a fresh tab finds a closed tab's doc (no server)	ok	ok
chromium	…time to find it, from storage	28 ms (22–38)	28 ms (28–33)
chromium	…and every edit made before the close is in it	ok	ok
chromium	edits from tabs closed right after editing all survive	ok	ok
chromium	…or at least 5s later	ok	ok
chromium	find a doc another tab just created	34 ms (34–35)	34 ms (32–36)	−0%
chromium	…and every such find() succeeded within 5s	ok	ok
chromium	…finds that settled unavailable first (of 2)	0	0
chromium	edit → seen in 2 other tabs	5 ms (5–6)	5 ms (5–5)	−6%
chromium	…every edit reached every other tab within 5s	ok	ok
chromium	edit → server holds our heads	126 ms (124–140)	125 ms (125–125)	−1%
chromium	…the server confirmed every edit within 5s	ok	ok
chromium	…and a stranger gets the whole doc from the server	ok	ok
chromium	renderer memory, 1 tab	357 MB (356–367)	357 MB (357–360)
chromium	renderer memory, 10 tabs	1900 MB (1884–1906)	1899 MB (1890–1900)	−0%
firefox	boot → repo, first tab (1 tabs)	554 ms (554–583)	567 ms (548–581)	+2%
firefox	boot → server connected, first tab (1 tabs)	970 ms (964–1071)	998 ms (964–1005)	+3%
firefox	renderer memory, all tabs + workers (1 tabs)	–	–
firefox	renderer processes (1 tabs)	–	–
firefox	boot → repo, first tab (3 tabs)	539 ms (536–598)	573 ms (538–577)	+6%
firefox	boot → repo, last tab (3 tabs)	414 ms (410–420)	404 ms (397–437)	−3%
firefox	boot → server connected, first tab (3 tabs)	1079 ms (995–1081)	1049 ms (1010–1143)	−3%
firefox	renderer memory, all tabs + workers (3 tabs)	–	–
firefox	renderer processes (3 tabs)	–	–
firefox	boot → repo, first tab (10 tabs)	580 ms (577–669)	560 ms (559–566)	−3%
firefox	boot → repo, last tab (10 tabs)	453 ms (432–463)	423 ms (407–429)	−7%
firefox	boot → server connected, first tab (10 tabs)	1126 ms (1124–1174)	1105 ms (1053–1118)	−2%
firefox	renderer memory, all tabs + workers (10 tabs)	–	–
firefox	renderer processes (10 tabs)	–	–
firefox	sync still works after the first tab closes	ok	ok
firefox	edit → seen + confirmed, after first tab closed	169 ms (166–171)	173 ms (173–179)	+2%
firefox	server link seen down while offline	ok	ok
firefox	…and the server did not see the offline edits	ok	ok
firefox	tabs converged while offline, over a local channel	ok	ok
firefox	offline edits in two tabs both survive reconnect	ok	ok
firefox	reconnect → tabs converged (only where they hadn't already)	–	–
firefox	…and a fresh tab sees both	ok	ok
firefox	boot → doc open, tab 1	1095 ms (1087–1169)	1107 ms (1100–1119)	+1%
firefox	boot → doc open, tab 2	529 ms (517–531)	530 ms (516–551)	+0%
firefox	boot → doc open, tab 10	503 ms (487–523)	554 ms (494–578)	+10%
firefox	open 40 tabs, wall clock	25821 ms (25447–26850)	26255 ms (25589–26646)	+2%
firefox	boot → repo, last of 40 tabs	224 ms (194–246)	248 ms (228–312)	+11%
firefox	boot → linked, last of 40 tabs	–	–
firefox	boot → server connected, last of 40 tabs	744 ms (642–748)	763 ms (726–834)	+3%
firefox	renderer memory, 40 tabs	–	–
firefox	renderer processes, 40 tabs	–	–
firefox	39 tabs find the doc: median	395 ms (394–420)	403 ms (394–419)	+2%
firefox	39 tabs find the doc: slowest	406 ms (404–429)	417 ms (400–426)	+3%
firefox	…all 39 found it	ok	ok
firefox	…finds that needed a retry (of 39)	0	0
firefox	edit → seen in 39 tabs: median tab	130 ms (127–132)	136 ms (128–152)	+4%
firefox	edit → seen in 39 tabs: slowest tab	211 ms (210–212)	226 ms (211–315)	+7%
firefox	…tabs that saw every edit (of 39)	39	39
firefox	edit → server holds our heads (40 tabs)	375 ms (373–378)	392 ms (378–395)	+5%
firefox	…server confirmed every edit (40 tabs)	ok	ok
firefox	…longest main-thread stall in tab 0 during the edits	143 ms (123–200)	141 ms (130–142)	−2%
firefox	sync rounds per sibling edit, non-editing tab	0	0
firefox	server bytes received per edit per tab	–	–
firefox	storage writes (saveBatch) per edit per tab	–	–
firefox	worker errors (40 tabs)	–	–
firefox	a fresh tab finds a closed tab's doc (no server)	ok	ok
firefox	…time to find it, from storage	34 ms (33–69)	32 ms (30–34)	−6%
firefox	…and every edit made before the close is in it	ok	ok
firefox	edits from tabs closed right after editing all survive	ok	ok
firefox	…or at least 5s later	ok	ok
firefox	find a doc another tab just created	33 ms (31–33)	33 ms (32–34)	+2%
firefox	…and every such find() succeeded within 5s	ok	ok
firefox	…finds that settled unavailable first (of 2)	0	0
firefox	edit → seen in 2 other tabs	18 ms (17–18)	18 ms (17–18)	−1%
firefox	…every edit reached every other tab within 5s	ok	ok
firefox	edit → server holds our heads	129 ms (129–132)	128 ms (127–135)	−1%
firefox	…the server confirmed every edit within 5s	ok	ok
firefox	…and a stranger gets the whole doc from the server	ok	ok
webkit	boot → repo, first tab (1 tabs)	505 ms (503–509)	507 ms (501–534)	+0%
webkit	boot → server connected, first tab (1 tabs)	574 ms (566–575)	591 ms (564–608)	+3%
webkit	renderer memory, all tabs + workers (1 tabs)	–	–
webkit	renderer processes (1 tabs)	–	–
webkit	boot → repo, first tab (3 tabs)	504 ms (503–520)	527 ms (517–537)	+5%
webkit	boot → repo, last tab (3 tabs)	420 ms (404–423)	428 ms (417–440)	+2%
webkit	boot → server connected, first tab (3 tabs)	589 ms (583–607)	596 ms (578–619)	+1%
webkit	renderer memory, all tabs + workers (3 tabs)	–	–
webkit	renderer processes (3 tabs)	–	–
webkit	boot → repo, first tab (10 tabs)	503 ms (488–513)	514 ms (510–538)	+2%
webkit	boot → repo, last tab (10 tabs)	441 ms (434–443)	426 ms (421–430)	−3%
webkit	boot → server connected, first tab (10 tabs)	592 ms (590–600)	586 ms (579–603)	−1%
webkit	renderer memory, all tabs + workers (10 tabs)	–	–
webkit	renderer processes (10 tabs)	–	–
webkit	sync still works after the first tab closes	ok	ok
webkit	edit → seen + confirmed, after first tab closed	62 ms	56 ms (55–68)	−10%
webkit	server link seen down while offline	ok	ok
webkit	…and the server did not see the offline edits	ok	ok
webkit	tabs converged while offline, over a local channel	ok	ok
webkit	offline edits in two tabs both survive reconnect	ok	ok
webkit	reconnect → tabs converged (only where they hadn't already)	–	–
webkit	…and a fresh tab sees both	ok	ok
webkit	boot → doc open, tab 1	725 ms (713–736)	715 ms (706–733)	−1%
webkit	boot → doc open, tab 2	549 ms (526–585)	542 ms (532–554)	−1%
webkit	boot → doc open, tab 10	594 ms (589–594)	556 ms (530–583)	−6%
webkit	open 40 tabs, wall clock	34491 ms (34486–34634)	34468 ms (34308–34899)	−0%
webkit	boot → repo, last of 40 tabs	226 ms (212–279)	245 ms (229–290)	+8%
webkit	boot → linked, last of 40 tabs	–	–
webkit	boot → server connected, last of 40 tabs	535 ms (532–637)	519 ms (502–548)	−3%
webkit	renderer memory, 40 tabs	–	–
webkit	renderer processes, 40 tabs	–	–
webkit	39 tabs find the doc: median	561 ms (557–677)	565 ms (523–659)	+1%
webkit	39 tabs find the doc: slowest	657 ms (647–874)	1080 ms (689–1105)	+64%
webkit	…all 39 found it	ok	ok
webkit	…finds that needed a retry (of 39)	0	0
webkit	edit → seen in 39 tabs: median tab	105 ms (101–123)	107 ms (102–130)	+2%
webkit	edit → seen in 39 tabs: slowest tab	313 ms (266–331)	272 ms (240–340)	−13%
webkit	…tabs that saw every edit (of 39)	39	39
webkit	edit → server holds our heads (40 tabs)	331 ms (312–332)	332 ms (329–336)	+0%
webkit	…server confirmed every edit (40 tabs)	ok	ok
webkit	…longest main-thread stall in tab 0 during the edits	90 ms (55–116)	70 ms (38–84)	−22%
webkit	sync rounds per sibling edit, non-editing tab	0	0
webkit	server bytes received per edit per tab	–	–
webkit	storage writes (saveBatch) per edit per tab	–	–
webkit	worker errors (40 tabs)	–	–
webkit	a fresh tab finds a closed tab's doc (no server)	ok	ok
webkit	…time to find it, from storage	101 ms (95–103)	97 ms (92–101)	−4%
webkit	…and every edit made before the close is in it	ok	ok
webkit	edits from tabs closed right after editing all survive	ok	ok
webkit	…or at least 5s later	ok	ok
webkit	find a doc another tab just created	56 ms (52–59)	55 ms (53–56)	−3%
webkit	…and every such find() succeeded within 5s	ok	ok
webkit	…finds that settled unavailable first (of 2)	0	0
webkit	edit → seen in 2 other tabs	15 ms (14–16)	16 ms (15–17)	+7%
webkit	…every edit reached every other tab within 5s	ok	ok
webkit	edit → server holds our heads	33 ms (32–36)	33 ms (33–35)	+2%
webkit	…the server confirmed every edit within 5s	ok	ok
webkit	…and a stranger gets the whole doc from the server	ok	ok

[github-actions]

✅ Patchwork glance ready

https://patchwork-preview-468.patchwork.inkandswitch.com

A peek at inkandswitch/patchwork.inkandswitch.com, built with the @inkandswitch/patchwork- packages as of this PR at a5938a4.