Skip to content

Commit 50c8fe5

Browse files
committed
article touch ups
1 parent fbb258a commit 50c8fe5

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

src/content/docs/articles/tpcc-analysis-jemalloc-mimalloc-tcmalloc-tidesql-and-innodb-in-mariadb-v11-8-6.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ head:
2222

2323
*published on April 22nd, 2026*
2424

25-
Well I had a thought recently and it was to run analysis with different allocators running in TidesDB in which is the lower level component for the MariaDB plugin <a href="/reference/tidesql">TideSQL</a>. In TidesDB you can configure jemalloc, mimalloc, or tcmalloc as the allocator when building. I've run this analysis using <a href="https://hammerdb.com">HammerDB</a> TPROC-C and a custom <a href="/mariadb-11-8-6-innodb-and-tidesql-v4-2-4-tpc-c/hammerdb_runner.sh">script</a> to automate the processes.
25+
It's been on my mind for a while to run analysis with different allocators running in TidesDB in which is the lower level component for the MariaDB plugin <a href="/reference/tidesql">TideSQL</a>. In TidesDB you can configure jemalloc, mimalloc, or tcmalloc as the allocator when building. I've run this analysis using <a href="https://hammerdb.com">HammerDB</a> TPROC-C and a custom <a href="/mariadb-11-8-6-innodb-and-tidesql-v4-2-4-tpc-c/hammerdb_runner.sh">script</a> to automate the processes.
2626

2727

2828
When installing TideSQL you can specify the allocator to build with TidesDB, the installer does all the mapping for you

0 commit comments

Comments
 (0)