Update UsingGperftoolsInCH.md

docs/developers/UsingGperftoolsInCH.md

@@ -4,6 +4,9 @@ We need using gpertools to find the memory or CPU issue. That's what this docume
 Install gperftools as described in https://github.com/gperftools/gperftools.
 We get the library and the command line tools.
 
+## Compiler libch.so
+Disable jemalloc `-DENABLE_JEMALLOC=OFF` in cpp-ch/CMakeLists.txt, and recompile libch.so.
+
 ## Run Gluten with gperftools
 For Spark on Yarn, we can change the submit script to run Gluten with gperftools.
 Add the following to the submit script:
@@ -18,4 +21,4 @@ export LD_PRELOAD=$tcmalloc_path,libch.so # load the library in the driver
 ## Analyze the result
 We can get the result in the path we set in the previous step. For example, we can get the result in `/tmp/gluten_heap_perf`. We can use the following website to analyze the result:
 https://gperftools.github.io/gperftools/heapprofile.html
-https://gperftools.github.io/gperftools/cpuprofile.html
+https://gperftools.github.io/gperftools/cpuprofile.html