URLSearchParams

[keithamus]

During the May monthly meeting @danielroe pointed out that URLSearchParams is slow compared to the ecosystem packages.

@43081j has some more detail on this, and provided benchmarks:

Results in Chrome:

Task name	Latency avg (ns)	Latency med (ns)	Throughput avg	Throughput med	Samples
picoquery	407.32 ± 1.96%	0.00 ± 0.00	2445117 ± 0.01%	2455059 ± 0	2455059
qs	1672.8 ± 2.05%	0.00 ± 0.00	598001 ± 0.03%	597787 ± 0	597787
fast-querystring	351.35 ± 1.96%	0.00 ± 0.00	2836188 ± 0.01%	2846141 ± 0	2846426
URLSearchParams	952.61 ± 2.12%	0.00 ± 0.00	1040459 ± 0.02%	1049751 ± 0	1049856

Chrome's source for URLSearchParams. I've raised crbug 513276599 to track this.

Results in Firefox:

Task name	Latency avg (ns)	Latency med (ns)	Throughput avg (ops/s)	Throughput med (ops/s)
picoquery	205.28 ± 6.20%	0.00 ± 0.00	4870484 ± 0.00%	4871484 ± 0
qs	980.51 ± 6.20%	0.00 ± 0.00	1018874 ± 0.01%	1019873 ± 0
fast-querystring (no nesting)	161.78 ± 6.20%	0.00 ± 0.00	6180349 ± 0.00%	6181349 ± 0
URLSearchParams (no nesting)	602.73 ± 6.37%	0.00 ± 0.00	1658139 ± 0.00%	1659126 ± 0

Firefox's source for URLSearchParams. I've raised Bug 2039814 to investigate.

The takeaway, it seems, is that people aren't using URLSearchParams when speed matters. We should investigate this further. There may be opportunities to speed up URLSearchParams to reach parity (or greater) in the browsers.