{"id":407,"date":"2011-01-24T10:55:57","date_gmt":"2011-01-24T15:55:57","guid":{"rendered":"http:\/\/hstore.cs.brown.edu\/"},"modified":"2012-07-16T11:32:21","modified_gmt":"2012-07-16T15:32:21","slug":"profiling","status":"publish","type":"page","link":"https:\/\/hstore.cs.brown.edu\/documentation\/debugging\/profiling\/","title":{"rendered":"Profiling H-Store using JProfiler"},"content":{"rendered":"
These instructions are for profiling the H-Store execution front-end using JProfiler<\/a> and Eclipse. The following steps are an adaption of the instructions on how Debug H-Store in Eclipse<\/a>. This has been tested on Eclipse 3.5 and 3.7.<\/p>\n You can add a trigger that causes JProfiler to only start collecting profile information when the first transaction request arrives from a client. This will avoid adding a lot of additional data just data loading portion of a benchmark run.<\/p>\n\n
\n
\ncd ${JPROFILER_HOME}\/bin\/linux-x64\r\nmv libstdc++.so.6 ORIG-libstdc++.so.6\r\nln -s \/usr\/lib\/x86_64-linux-gnu\/libstdc++.so.6\r\n<\/pre>\n<\/ul>\n
\n
catalog.jar=tpcc.jar\r\nsite.id=0\r\nconf=${HSTORE_HOME}\/properties\/default.properties\r\n<\/pre>\n<\/li>\n
-ea\r\n-server\r\n-Xmx2048m\r\n-Xcheck:jni\r\n-Djava.library.path=${HSTORE_HOME}\/obj\/release\/nativelibs:\\\r\n ${JPROFILER_HOME}\/bin\/linux-x64:\/usr\/lib\r\n<\/pre>\n<\/li>\n
${HSTORE_HOME}<\/pre>\n<\/li>\n
LD_LIBRARY_PATH \u2192 \/usr\/lib:${env_var:LD_LIBRARY_PATH}<\/pre>\n<\/li>\n<\/ul>\n<\/li>\n
ant build<\/tt> hstore-prepare<\/tt> -Dproject=tpcc<\/pre>\n<\/li>\n
\nWait just a few seconds and then launch the hstore-benchmark<\/tt> command shown below. The nostart<\/tt> option is a comma-separated list of the sites that will be started externally from the BenchmarkController<\/a> framework:<\/p>\nant hstore-benchmark<\/tt> -Dproject=tpcc -Dnostart=0<\/pre>\n<\/li>\n<\/ol>\n
Adding Triggers<\/h2>\n
\n