Postmark introduction and installation configuration

Postmark introduction and installation configuration 1. introduction Postmark is developed by NetApp, a famous NAS provider, to test the backend storage performance of its products. Postmark is mainly used to test the performance of a file system in a mail or e-commerce system. This type of application features: frequent and massive storage... postmark introduction and installation configuration 1. introduction Postmark is developed by NetApp, a famous NAS provider, to test the backend storage performance of its products. Postmark is used to test the performance of a file system in a mail or e-commerce system. This type of application features frequent and massive access to small files.
The test principle of Postmark is to create a test file pool. The maximum and minimum file length can be set, and the total data volume is certain. After the File Pool is created, Postmark performs a series of transaction operations on the File Pool. based on the statistics from the actual application, set each transaction to include one creation or deletion operation and one read or addition operation. in some cases, the cache policy of the file system may affect the performance, postmark can offset this impact by modifying the ratio of creation, deletion, and read/add operations. After the transaction operation is complete, the Post operation deletes the File Pool, ends the test, and outputs the result.
Postmark uses a random number to generate the serial number of the operated file, so that the test is closer to the practical application. Important output data in the output results include the total test time, the average number of transactions completed per second, and the average number of files created and deleted per second in transaction processing, and the average transmission speed of reading and writing. II. postmark usage (two methods): 1. use the configuration file to put all the configuration commands and run into the file. the postmark will automatically read the configuration file example: set size 10000 50000 set transactions 5000 set number 5000runquit run. /postmark XXX. cfg 2. command line mode. /postmark enters the command line mode, and then enters the corresponding command for configuration. The run command runs postmark according to the current configuration and runs the commands in the preceding configuration file in the command line in sequence. The results are the same, there is no difference, for example: [root @ msns719 pm-test] #. /postmark-1.51PostMark v1.51: 8/14/01 pm> set size 10000 20000pm> set number 1000 pm> set transactions 50000pm> run 3. command parsing Set size min_size max_size sets the upper and lower limits of the file size set number XXX sets the number of concurrent files set seed XXX sets the random seed set transactions XXX sets the number of transactions set location sets the working directory, should be an existing directory, by default, the current directory + name weight-namename weight is used to delete all original directories, then add the directory set subdirectory n in the parameter to set the number of subdirectories in each working directory set read nset write n set the size of the read/write block set buffering true/false true buffered (defoult) false nobufferedset bias read n indicates the proportion of read in read/append n/10 set bias create n create/delete Proportion n/10 set report verbose (default)/terse sets the report mode. the output in terse mode has no text description, so that after multiple tests are run through batch processing, use excel to analyze the result run [filename] run postmark, and output the result to stdout or file filenameshow [filename] to output the current setting helpquit 4. instance test: configuration file pm. cfg: set location/mnt/testaudit/pm-testset subdirectories 1 set size 10000 50000 set transactions 5000 set number 5000 runquit run [root @ RedHat postmark] #. /postmark pm. wrote postmark v1.5: 3/27/01 Reading configura Tion from file 'PM. cfg 'creating files... donePerforming transactions .......... doneDeleting files... doneTime: 39 seconds total 16 seconds of transactions (312 per second) Files: 7455 created (191 per second) Creation alone: 5000 files (500 per second) Mixed with transactions: 2455 files (153 per second) 2553 read (159 per second) 2447 appended (152 per second) 7455 deleted (191 per second) Deletion Alone: 4910 files (377 per second) Mixed with transactions: 2545 files (159 per second) Data: 77.04 megabytes read (1.98 megabytes per second) 234.28 megabytes written (6.01 megabytes per second) [root @ RedHat postmark] # This benchmark can also be changed to a multi-threaded testing environment.