Searched refs:benchmarks (Results 1 – 9 of 9) sorted by relevance
23 …](http://ceed.exascaleproject.org/software/), a collection of software benchmarks, miniapps, libra…330 A sequence of benchmarks for all enabled backends can be run using:333 $ make benchmarks336 The results from the benchmarks are stored inside the `benchmarks/` directory and they can be viewe…339 $ cd benchmarks344 Using the `benchmarks` target runs a comprehensive set of benchmarks which may take some time to ru…345 Subsets of the benchmarks can be run using the scripts in the `benchmarks` folder.347 For more details about the benchmarks, see the `benchmarks/README.md` file.
842 .PHONY: $(bench_targets) benchmarks844 cd benchmarks && ./benchmark.sh --ceed "$(BACKENDS)" -r $(*).sh845 benchmarks: $(bench_targets) target904 $(RM) benchmarks/*output.txt
1009 EXCLUDE = benchmarks \
36 Note that in order for the benchmarks to make sense for `magma` backends, the
23 The results from the benchmarks are written to files named `*-output.txt`.
40 The resulting log file can be read by the Python plotting scripts in `benchmarks/`.
5 C This file is part of CEED, a collection of benchmarks, miniapps, software
147 # Performance benchmarks