10 More Discussions You Might Find Interesting
1. High Performance Computing
Hi,
I compiled Linpack with ATLAS for test.
What other libraries except ATLAS can be used to test? (2 Replies)
Discussion started by: PtaQ
2 Replies
2. High Performance Computing
I'm trying to compile Linpack on a Ubuntu cluster. I'm running MPI. I've modified the following values to fit my system TOPdir MPdir LAlib CC LINKER.
When compiling I get the following error: (the error is at the end, the other errors in between are because I've ran the script several times so... (0 Replies)
Discussion started by: JPJPJPJP
0 Replies
3. UNIX for Advanced & Expert Users
Hi all,
I have one libxxx.so file ( which I got from a third party ). We use shared library libxxx.sl . Is there any way to convert the .so file to .sl file ?
Thanks in advance
- M (3 Replies)
Discussion started by: kanu_kanu
3 Replies
4. Shell Programming and Scripting
Hi,
I have a requirement to capture file time stamp and compare with current system time. I am using HP-AUX K-shell.
Below is what i have done
Getting current date into myfile2
---------------------------------
date +%Y%m%d%H%M%S > myfile2
20091110132800
Getting the file date into... (5 Replies)
Discussion started by: chinniforu2003
5 Replies
5. Shell Programming and Scripting
How to convert Nov 10 14:20 to YYYYMMDDHHMMSS in unix
I am using K-shell HP-AUX (1 Reply)
Discussion started by: chinniforu2003
1 Replies
6. Shell Programming and Scripting
I need to convert an epoch time from a file into a standard UTC time and output it in the same format but I'm not sure what's the best approach
here's the input file and the bold part is what I need to convert.
1,1,"sys1",60,300000
2,"E:",286511144960
3,1251194521,"E:",0,0... (2 Replies)
Discussion started by: satchy321
2 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
When using ls -l I get the details of a filename with the date in the format
Jun 22, is
I need to get it as 22/06, is there any ls command that would do this or is there a way to do this ? (8 Replies)
Discussion started by: happyrain
8 Replies
8. High Performance Computing
Hi guys,
I am having some issues tuning the HPL.dat file for the Linpack benchmark test across 2 nodes. I am very new to this with minimal Linux experience, however i am trying my luck.
The specs for the two nodes are:
3GHZ QX6850 CORE 2 EXTREME (QUAD CORE)
4GB RAM
I have been typing these... (1 Reply)
Discussion started by: mercthunder
1 Replies
9. Shell Programming and Scripting
hi all
i have a file like
151125
25252
2452567
253464576
255
i want this file to be like
'151125','25252','2452567','253464576','255'
please help
thanks (3 Replies)
Discussion started by: infyanurag
3 Replies
10. UNIX for Advanced & Expert Users
Dear friends,
i am writing sh shell script
I have a file containing binary data.
like this.
010101010101010101101010101010100001010101010101001.
i want to read some particular bits and convert it into decimal valuse.
example.
1.first i want to read 5 bits and convert it into... (1 Reply)
Discussion started by: rajan_ka1
1 Replies
OBNAM-BENCHMARK(1) General Commands Manual OBNAM-BENCHMARK(1)
NAME
obnam-benchmark - benchmark obnam
SYNOPSIS
obnam-benchmark [--config=FILE] [--description=DESCRIPTION] [--drop-caches] [--dump-config] [--dump-memory-profile=METHOD]
[--dump-setting-names] [--file-size=SIZE] [--generate-manpage=TEMPLATE] [--generations=N] [-h] [--help] [--larch-branch=DIR]
[--list-config-files] [--log=FILE] [--log-keep=N] [--log-level=LEVEL] [--log-max=SIZE] [--log-mode=MODE] [--no-default-configs]
[--obnam-branch=DIR] [--output=FILE] [--profile-name=PROFILE-NAME] [--results=DIR] [--seivot-branch=DIR] [--seivot-log=SEIVOT-LOG]
[--sftp-delay=SFTP-DELAY] [--size=PAIR] [--use-sftp-repository] [--use-sftp-root] [--verify] [--version] [--with-encryption] [FILE]...
DESCRIPTION
obnam-benchmark benchmarks the obnam(1) backup application, by measuring how much time it takes to do a backup, restore, etc, in various
scenarios. obnam-benchmark uses the seivot(1) tool for actually running the benchmarks, but makes some helpful assumptions about things,
to make it simpler to run than running seivot directly.
Benchmarks are run using two different usage profiles: mailspool (all files are small), and mediaserver (all files are big). For each pro-
file, test data of the desired total size is generated, backed up, and then several incremental generations are backed up, each adding some
more generated test data. Then other operations are run against the backup repository: restoring, listing the contents of, and removing
each generation.
The result of the benchmark is a .seivot file per profile, plus a Python profiler file for each run of obnam. These are stored in
../benchmarks. A set of .seivot files can be summarized for comparison with seivots-summary(1). The profiling files can be viewed with
the usual Python tools: see the pstats module.
The benchmarks are run against a version of obnam checked out from version control. It is not (currently) possible to run the benchmark
against an installed version of obnam. Also the larch Python library, which obnam needs, needs to be checked out from version control.
The --obnam-branch and --larch-branch options set the locations, if the defaults are not correct.
OPTIONS
--config=FILE
add FILE to config files
--description=DESCRIPTION
describe benchmark
--drop-caches
drop kernel buffer caches
--dump-config
write out the entire current configuration
--dump-memory-profile=METHOD
make memory profiling dumps using METHOD, which is one of: none, simple, meliae, or heapy (default: simple)
--dump-setting-names
write out all names of settings and quit
--file-size=SIZE
how big should files be?
--generate-manpage=TEMPLATE
fill in manual page TEMPLATE
--generations=N
benchmark N generations (default: 5)
-h, --help
show this help message and exit
--larch-branch=DIR
use DIR as the larch branch (default: /sbuild-nonexistent/larch/trunk)
--list-config-files
list all possible config files
--log=FILE
write log entries to FILE (default is to not write log files at all); use "syslog" to log to system log, or "none" to disable log-
ging
--log-keep=N
keep last N logs (10)
--log-level=LEVEL
log at LEVEL, one of debug, info, warning, error, critical, fatal (default: debug)
--log-max=SIZE
rotate logs larger than SIZE, zero for never (default: 0)
--log-mode=MODE
set permissions of new log files to MODE (octal; default 0600)
--no-default-configs
clear list of configuration files to read
--obnam-branch=DIR
use DIR as the obnam branch to benchmark (default: .)
--output=FILE
write output to FILE, instead of standard output
--profile-name=PROFILE-NAME
short name for benchmark scenario
--results=DIR
put results under DIR (../benchmarks)
--seivot-branch=DIR
use DIR as the seivot branch (default: installed seivot)
--seivot-log=SEIVOT-LOG
seivot log setting
--sftp-delay=SFTP-DELAY
add artifical delay to sftp transfers (in milliseconds)
--size=PAIR
add PAIR to list of sizes to benchmark (e.g., 10g/1m)
--use-sftp-repository
access the repository over SFTP (requires ssh to localhost to work)
--use-sftp-root
access the live data over SFTP (requires ssh to localhost to work)
--verify
verify restores
--version
show program's version number and exit
--with-encryption
run benchmark using encryption
ENVIRONMENT
TMPDIR This variable must be set. It controls where the temporary files (generated test data) is stored. If this variable was not set,
they'd be put into /tmp, which easily fills up, to the detriment of the entire system. Thus. obnam-benchmark requires that the lo-
cation is set explicitly. (You can still use /tmp if you want, but you have to set TMPDIR explicitly.)
FILES
../benchmarks/
The default directory where results of the benchmark are stored, in a subdirectory named after the branch and revision numbers.
EXAMPLE
To run a small benchmark:
TMPDIR=/var/tmp obnam-benchmark --size=10m/1m
To run a benchmark using existing data:
TMPDIR=/var/tmp obnam-benchmark --use-existing=$HOME/Mail
To view the currently available benchmark results:
seivots-summary ../benchmarks/*/*mail*.seivot | less -S
seivots-summary ../benchmarks/*/*media*.seivot | less -S
(You need to run seivots-summary once per usage profile.)
SEE ALSO
obnam(1), seivot(1), seivots-summary(1).
OBNAM-BENCHMARK(1)