Search Results for "time code"

Most test frameworks for C require a lot of boilerplate code to set up tests and test suites -- you need to create a main, then register new test suites, then register the tests within these suites, and finally call the right functions. This gives the user great control, at the unfortunate cost of simplicity. Criterion follows the KISS principle, while keeping the control the user would have with other frameworks.

...The client sends whatever information the user puts on the command-line to the back-end daemon via TCP. Upon successful transmission, the client exits. On failure, it backs off and retries until its life-time timer expires. The back-end daemon accepts data from Syslogd2 or its own client and inserts that data (and envelope information) into one or more databases using MySql client library or dbi drivers (also on SourceForge). The client needs no configuration (all input is via command-line). It is intended for hosts to make database entries without needing database client or interface code. ...

A collection of library code and tools for application execution profiling and performance testing. You can create stopwatches to time select portions of your code. You can measure differences (often to sub-millisecond accuracy) between clocks on different machines. You can log application events in a .csv format for subsequent analysis. You can also generate CPU loading logs in a .csv format.

BEMAP (BEnchMarks for Automatic Parallelizer) is a benchmark used to measure performance for an automatic parallelizer. All OpenCL code benchmarks covered in this project are done step-by-step along with hand-tunning. Each tuning step executional time are measured in details with a comprehensive user interface and help option. The exact implementation in native code (C++) is also provided in each project folder for reference. By using these benchmarks, one may analyze: 1. ...

This profiler (JRE 1.5.0 only) uses JVMTI and native bytecode instrumentation for the analysis of the heap, reachable objects, execution time, garbage collection efficiency, code coverage and thread contention. No preparation steps required in build.