bench(interlace): adding test bench tools to justify performance issues

[freemine]

Description

it seems that TAOS_STMT_OPTIONS::singleStbInsert / singleTableBindOnce does NOT bring the performance improvements as stated in the documentation.
this test benchmark tool is to demon the potential issue.

pls also be kindly noted: the tool is vibe-generated by AI, and no thorough review yet, thus there might be error big or small, and conclusion above might be wrong.

if there's any official tool to demonstrate the same issue, pls let me know and i might be able to compare.

thx!

to produce as an example:

./debug/build/bin/stmtPerfBench --api stmt2 --mode all --scenario all --seed 1 --db test --drop-db yes --verify yes --verbose-metrics yes --cycles 10  --rows-per-table 1000 --batch-rows 1 --wrarmup 1

Issue(s)

Checklist

Please check the items in the checklist if applicable.

• Is the user manual updated?
• Are the test cases passed and automated?
• Is there no significant decrease in test coverage?

[gemini-code-assist]

Code Review

This pull request introduces a performance benchmarking tool for the client library, specifically targeting the STMT and STMT2 APIs. The implementation includes the core benchmark logic, a shared utility library, and a comprehensive suite of unit tests. The review feedback focuses on improving cross-platform portability by replacing non-standard functions like usleep and getpid, enhancing code readability through explicit struct member initialization, and adopting more idiomatic C++ patterns for error handling and file operations.

[gemini-code-assist]

usleep is deprecated and not portable as it's not available on Windows. For better portability and to adhere to modern C++ standards, please use std::this_thread::sleep_for from the <thread> header. You already include <chrono>, so you would just need to add an include for <thread>.

Suggested change

	usleep(200 * 1000);
	std::this_thread::sleep_for(std::chrono::milliseconds(200));

[gemini-code-assist]

getpid is not portable and is unavailable on Windows. To ensure this tool can be compiled and run on different operating systems, please use conditional compilation to provide a platform-specific implementation (e.g., _getpid from <process.h> on Windows).

[gemini-code-assist]

Using const_cast to remove const is dangerous as it subverts the type system and can lead to undefined behavior if the underlying data is modified. The taos_stmt2_bind_param API appears to require a non-const char**. If you are certain the API does not modify the strings, this may work, but it's a significant code smell. It would be best to fix the API to accept const char* const*. If that's not feasible, please add a comment explaining why the const_cast is necessary and considered safe here.

[gemini-code-assist]

Using C-style aggregate initialization with positional values like {0, true, true} can be unclear about which member is being initialized. For better readability and maintainability, it's preferable to use C++ uniform initialization ({}) and then set the members explicitly by name. This makes the code self-documenting.

  TAOS_STMT_OPTIONS options{};
  options.enable_auto_bind = true;
  options.single_stb_bind = true;
  TAOS_STMT        *stmt = benchCase.mode == StmtPerfBenchMode::kInterlace ? taos_stmt_init_with_options(taos, &options)
                                                                            : taos_stmt_init(taos);

[gemini-code-assist]

The use of goto for error handling is generally discouraged in C++ as it can make the code harder to follow and maintain. Consider using more idiomatic C++ patterns like RAII (Resource Acquisition Is Initialization) with guard classes to handle cleanup automatically, or a do { ... } while (false) loop with break statements.

[gemini-code-assist]

This C-style aggregate initialization is not very readable. Please use C++ uniform initialization and set struct members explicitly by name to make the code's intent clearer.

Suggested change

	TAOS_STMT2_OPTION option = {0, benchCase.mode == StmtPerfBenchMode::kInterlace,
	benchCase.mode == StmtPerfBenchMode::kInterlace, NULL, NULL};
	TAOS_STMT2_OPTION option{};
	option.singleStbInsert = (benchCase.mode == StmtPerfBenchMode::kInterlace);
	option.singleTableBindOnce = (benchCase.mode == StmtPerfBenchMode::kInterlace);

[gemini-code-assist]

The ok variable and the cleanup block appear to be redundant. The ok variable is always true when this code is reached, making the if(!ok) block dead code. Since error paths return false directly, you can simplify this section by removing the ok variable and the cleanup logic, and simply returning true at the end of a successful execution.

  ok = true;

  taos_stmt2_close(stmt);
  return ok;

[gemini-code-assist]

For better C++ style, you can pass the std::string object directly to open() instead of converting it to a C-style string with .c_str(). The std::fstream methods have had overloads for std::string since C++11.

Suggested change

	fileOutput.open(config.outputFile.c_str(), std::ios::out | std::ios::trunc);
	fileOutput.open(config.outputFile, std::ios::out | std::ios::trunc);