|
|
Sponsored Content
Top Forums
UNIX for Advanced & Expert Users
any way to commit idle tasks in unix?
Post 302168781 by System Shock on Tuesday 19th of February 2008 12:49:16 PM
02-19-2008
Quote:
Why? Reproducibility of results.
Generally, when you publish benchmarks, you do so running no other programs. You may also try to turn off many background services/processes/whatever.
You do this so that other people running your benchmark on the same hardware are more likely to get the same result as you.
The more stuff besides your actual benchmark that can possibly be running during benchmarking, the less reproducible your results become.
The exception to these comments are when you specifically want to see how your task runs on a loaded system of some kind, but this is less common.
If unix simply lacks the functionality that windows has in this area--fine. Idle tasks suddenly running in the middle of your benchmark is usually a rare event. Its certainly more important that you do obvious simple things like make sure that no other non-idle tasks are running. But having an api for committing idle tasks like windows does certainly is icing on the cake, as it can eliminate the rare possibility.
Generally, when you publish benchmarks, you do so running no other programs. You may also try to turn off many background services/processes/whatever.
You do this so that other people running your benchmark on the same hardware are more likely to get the same result as you.
The more stuff besides your actual benchmark that can possibly be running during benchmarking, the less reproducible your results become.
The exception to these comments are when you specifically want to see how your task runs on a loaded system of some kind, but this is less common.
If unix simply lacks the functionality that windows has in this area--fine. Idle tasks suddenly running in the middle of your benchmark is usually a rare event. Its certainly more important that you do obvious simple things like make sure that no other non-idle tasks are running. But having an api for committing idle tasks like windows does certainly is icing on the cake, as it can eliminate the rare possibility.
, but I guess we are more concerned with performance under regular load, rather than matching numbers within platforms... One method that you could use to achieve something vaguely similar would be to run your unix test on single user mode; only a portion of services run when the box is running on single user mode. Any service that your particular application may need can be started, and you could kill whatever service may pop up during your benchmark (mostly killing the cron daemon would do).
|
|
8 More Discussions You Might Find Interesting
1. SCO
Hi,
Please let us know of any possiblity of identifying and killing unix proces invoked externally (by an external tool which does not create a session). 'who' command gives idle time of sessions. But what we are looking for is idle time of a process. 'ps' command gives the elapsed/running... (1 Reply)
Discussion started by: vbalajis
1 Replies
2. SCO
Hi.
Am a unix 5.o.5 user. I need to schedule a program to be running everyday at 12 midnight. How do i proceed. I need help.
Also what is the maximum size that sco unix can conveninetly handle. I keep getting this message. "Filesystem greater than device which it is curently located. Pls backup... (2 Replies)
Discussion started by: uzomaok
2 Replies
3. AIX
good morning
Can you explain to me what is a "commit" (aix 5.3) ?
There is no man for this command.
thank you (1 Reply)
Discussion started by: pascalbout
1 Replies
4. Shell Programming and Scripting
I would like to run a cvs diff to check which files have been changed and then cvs commit these changed files. Does anyone have a shell script which will automate this process? (1 Reply)
Discussion started by: alangibson
1 Replies
5. UNIX for Advanced & Expert Users
Hi ,
can u please any one of you give solution for this ..
when am tryring to commit files from the CVS in Myeclipse J2ee Environment . that i coundnt able to commit and getting the Following error message
cvs :'root' is not allowd to commit files'
am using redhat enterprise 5 Server . (1 Reply)
Discussion started by: rksubash
1 Replies
6. Shell Programming and Scripting
I am writing a unix shell script for the archive purge job.
During purging, the records will be deleted one by one. I didnot mention anything about db2 commit. By default, the records are commited one by one. Now I need to give commit for every 50 records deletion.
The deletion part is as... (0 Replies)
Discussion started by: kmanivan82
0 Replies
7. Shell Programming and Scripting
Hi All,
I have written a shell script in which i am updating records in a table. It is a PL/SQL block. I have to use PL/SQL block as i am using bms_application_info.set_module package
But the problem is once the script completes, i cannot see the updated records in Table. I mean result is... (0 Replies)
Discussion started by: Amit.Sagpariya
0 Replies
8. Shell Programming and Scripting
Is someone help me to achieve my goal
I am working on a script actually script is working fine .The goal of script is restrict the user for something like while he is doing tocommit in repository he will commit with comment and with some parameter....here I have one more requirement and that is... (0 Replies)
Discussion started by: anuragpgtgerman
0 Replies
LEARN ABOUT XFREE86
idle
IDLE(1) General Commands Manual IDLE(1) NAME
IDLE - An Integrated DeveLopment Environment for Python SYNTAX
idle [ -dins ] [ -t title ] [ file ...] idle [ -dins ] [ -t title ] ( -c cmd | -r file ) [ arg ...] idle [ -dins ] [ -t title ] - [ arg ...] DESCRIPTION
This manual page documents briefly the idle command. This manual page was written for Debian because the original program does not have a manual page. For more information, refer to IDLE's help menu. IDLE is an Integrated DeveLopment Environment for Python. IDLE is based on Tkinter, Python's bindings to the Tk widget set. Features are 100% pure Python, multi-windows with multiple undo and Python colorizing, a Python shell window subclass, a debugger. IDLE is cross-plat- form, i.e. it works on all platforms where Tk is installed. OPTIONS
-h Print this help message and exit. -n Run IDLE without a subprocess (see Help/IDLE Help for details). The following options will override the IDLE 'settings' configuration: -e Open an edit window. -i Open a shell window. The following options imply -i and will open a shell: -c cmd Run the command in a shell, or -r file Run script from file. -d Enable the debugger. -s Run $IDLESTARTUP or $PYTHONSTARTUP before anything else. -t title Set title of shell window. A default edit window will be bypassed when -c, -r, or - are used. [arg]* and [file]* are passed to the command (-c) or script (-r) in sys.argv[1:]. EXAMPLES
idle Open an edit window or shell depending on IDLE's configuration. idle foo.py foobar.py Edit the files, also open a shell if configured to start with shell. idle -est "Baz" foo.py Run $IDLESTARTUP or $PYTHONSTARTUP, edit foo.py, and open a shell window with the title "Baz". idle -c "import sys; print sys.argv" "foo" Open a shell window and run the command, passing "-c" in sys.argv[0] and "foo" in sys.argv[1]. idle -d -s -r foo.py "Hello World" Open a shell window, run a startup script, enable the debugger, and run foo.py, passing "foo.py" in sys.argv[0] and "Hello World" in sys.argv[1]. echo "import sys; print sys.argv" | idle - "foobar" Open a shell window, run the script piped in, passing '' in sys.argv[0] and "foobar" in sys.argv[1]. SEE ALSO
python(1). AUTHORS
Various. 21 September 2004 IDLE(1)