6 commits

Author	SHA1	Message	Date
Boshen	293668bebd	chore(tasks): parse regular expression in parser benchmark (#5212)	2024-08-26 13:11:09 +08:00
overlookmotel	6bc18e15e0	refactor(bench): reuse allocator in parser + lexer benchmarks (#3053) ... Re-use allocator in parser + lexer benchmarks. I believe this is the recommended usage when parsing a bunch of files - to re-use one allocator rather than create a fresh one for each run, so it makes sense to me that this is what the benchmark should measure. Doesn't show much difference on CodSpeed because it only runs the benchmark once, and it treats allocations as free anyway. But I imagine the difference may show up a bit more in a standard criterion benchmark.	2024-04-22 09:03:26 +08:00
Boshen	39f026f3e2	chore(benchmark): remove custom allocators because they are flaky (#2004)	2024-01-12 16:05:47 +08:00
Boshen	601153fe8f	refactor(benchmark): use more complicated files (#1811) ... closes #1806 --------- Co-authored-by: Dunqing <dengqing0821@gmail.com>	2023-12-25 17:27:02 +08:00
Boshen	2ba18e073c	fix(benchmark): use different data sets for benchmark and minifier test	2023-09-02 20:56:45 +08:00
Boshen	56aaf31fb1	refactor(benchmark): use codspeed for all benchmarks (#839)	2023-09-02 20:35:48 +08:00