Back to Blog
Parsec run5/4/2023 ![]() To compile all programs of the benchmark suite with the default configuration,īesides the regular configuration which can be altered to customize theīenchmark suite, PARSEC also uses build configurations. ![]() The following examples assume that the 'bin/' directory of PARSEC is in yourīefore compiling the PARSEC benchmarks, please change some variables in theįile "config/gcc.bldconf" such that the PARSEC command can locate the Support for other shells is currently not available. You can then start browsing the documentation by running man parsec'. If you work with the bash shell youĬan make use of it before you start working with PARSEC by executing Which modifies the environment in that way. A bash shell script env.sh' is provided in the root directory of the PARSEC distribution If you add the bin/' directory to the PATH environment variable and the man/' directory to the MANPATH variable then all tools and man pages are accessible at the command line without having to specify the full path every time. Parts of the source code is given in the man/' directory. Summary for each tool by invoking it with option '-h'.Ī full set of man pages documenting PARSEC, its tools and the most important Which will contain all output in the 'log/' directory. When you build and run PARSEC with 'parsecmgmt', it will create a log file 'bldconfdel' can be used to create and delete your own build configurations. Packages as well as perform other management operations. You can use them to customize and manage your installation of the benchmark PARSEC ships with several tools which are installed in the 'bin/' directory. Limited support exists for the following platforms, but not all benchmark PARSEC has been successfully tested on the following systems: Parallelization has its own requirements that have to be fulfilled in order toīe able to build and run workloads that use it. Many workloads support more than one parallelization. The PARSEC benchmarks have been parallelized with pthreads, OpenMP, TBB andĪtomic instructions. Required for temporary files, up to several GB if the whole suite is to beīuilt and executed in one run without cleaning up intermittently. To build packages and run them extra space is PARSEC occupies about 7 GB with a raw installation. PARSEC requires at least 8 GB, but we recommend 12 GB or more. Make sure you don't violate any license terms. You have to take appropriate steps yourself to We distribute the programs and their workloads bundled with PARSEC merely toĪllow PARSEC users a convenient access to them and because the license termsĪllow us do so in each case. Licenses for inputs canīe found in the 'inputs/' directory of the package. Licenses for source code canīe found in the 'src/' directory of each package. Some of the inputs have their own license, too. Each program uses its own license, which is different in some cases. The PARSEC framework itself is available under a liberal open source license,Īs explained in the file LICENSE which is in the same directory as this READMEįile. Supplied inputs in any way, make sure you understand all licenses involved. Licensesīefore you start using, modifying or distributing PARSEC, its programs or the The inputs for each program exhibit differentĬharacteristics such as execution time and working set size. PARSEC ships with predefined inputs that can be Build configurations contain information such as whichįeatures of the package should be enabled, which compilers to use and how the Each package can be compiled in a number of ways as determined byĪ build configuration. Packages correspond to benchmark programs, libraries and other essentialĬomponents. The PARSEC distribution is composed of packages and the PARSEC framework. The Princeton Application Repository for Shared-Memory Computers (PARSEC) is aĬollection of parallel programs which can be used for performance studies of In a global bldconf are preserved while building packages. Instead of calling gcc tools and overwritingĬFLAGS, CC, CFLAGS, and related environment variables set ![]()
0 Comments
Read More
Leave a Reply. |