Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Optimizing the system reliability Post 32719 by Deepa on Thursday 5th of December 2002 01:54:56 AM
Old 12-05-2002
Optimizing the system reliability

My product have around 10-15 programs/services running in the sun box, which together completes a task, sequentially. Several instances of the each program/service are running in the unix box, to manage the load and for risk-management reasons. As of now, we dont follow a strict strategy in computing how many instances of each program needs to be invoked to attain a good performance of the whole product.

Is there any strategy to be followed in determining the number of parallel instances of each program...of course, memory consumption, cpu load etc are to be considered for each instance?

Apologize, if this is not the right forum for posting this Q.
 

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Optimizing for a Speed-up

How would one go about optimizing this current .sh program so it works at a more minimal time. Such as is there a better way to count what I need than what I have done or better way to match patterns in the file? Thanks, #declare variables to be used. help=-1 count=0 JanCount=0 FebCount=0... (3 Replies)
Discussion started by: switch
3 Replies

2. UNIX and Linux Applications

Optimizing query

Hi All, My first thread to this sub-forum and first thread of this sub-forum :) Here it is, Am trying to delete duplicates from a table retaining just 1 duplicate value out of the duplicate records for example : from n records of a table out of which x are duplicates, I want to remove x... (15 Replies)
Discussion started by: matrixmadhan
15 Replies

3. High Performance Computing

High reliability web server - cluster, redundancy, etc

Hi. I am IT manager/developer for a small organization. I have been doing as-needed linux server administration for several years and am by no means an expert. I've built several of my own servers, and our org is currently using hosting services for our servers and I am relatively happy. We... (3 Replies)
Discussion started by: bsaadmin
3 Replies

4. AIX

MPIO reliability

Hi, we have a vew boxes using MPIO and they are connected to some virtualization software managing some disk subsystems, offering volumes to the AIX boxes. Sometimes when a cable has been plugged out for a test or when a real problem occurs, using lspath to show the state of the paths shows... (8 Replies)
Discussion started by: zaxxon
8 Replies

5. Shell Programming and Scripting

Optimizing the code

Hi, I have two files in the format listed below. I need to find out all values from field 12 to field 20 present in file 2 and list them in file3(format as file2) File1 : FEIN,CHRISTA... (2 Replies)
Discussion started by: nua7
2 Replies

6. Solaris

Reasons for NOT using LDOMs? reliability?

Dear Solaris Experts, We are upgrading from sun4u to T4 systems and one proposal is to use LDOMs and also zones within LDOMs. Someone advised using only zones and not LDOMs because the new machines have fewer chips and if a chip or a core fails then it doesn't impact the zones, but impacts... (3 Replies)
Discussion started by: User121
3 Replies

7. Web Development

Optimizing JS and CSS

Yes. Got few suggestions. - How about minifying resources - mod_expires - Service workers setup https://www.unix.com/attachments/web-programming/7709d1550557731-sneak-preview-new-unix-com-usercp-vuejs-demo-screenshot-png (8 Replies)
Discussion started by: Akshay Hegde
8 Replies
dzhandle(1)						      General Commands Manual						       dzhandle(1)

NAME
dzhandle -- Debian/Ubuntu Zope packages handling command line utility SYNOPSIS
dzhandle [options] action [action options] DESCRIPTION
dzhandle is the command-line utility for handling Zope servers, instances and products. It is a system administration tool and a Debian/Ubuntu maintainer's helper script at the same time: using dzhandle you can manage your Zope installations, create instances, add Zope products to them, start and stop them, but it is also used by the Debian/Ubuntu Zope packages for their installation and removal. OPTIONS
-h, --help Print usage information and exit -f, --force Force things, for example file overwriting or removing -z, --zope-version=ZVERSIONS limit actions to a comma separated list of zope versions; default behaviour is to act on all zope versions available -u, --user=USER[:GROUP] User/Group ownership for new and copied files -c, --config-file=FILE Configuration file; default is /etc/dzhandle.conf -v, --verbose Enable verbose mode (not yet implemented) -n, --dry-run Do not execute commands, print only them (not yet implemented) ACTIONS (instances handling) make-instance <instance> -m AMODE [<options>] Create a new instance running Zope version specific mkzopeinstance. -m AMODE, --addon-mode=AMODE Which products and extensions will be installed: `all' means every product or extension available will be automatically installed, `manual' means that the products or extensions will be installed manually through dzhandle. This option is mandatory. -t ATECHNIQUE, --addon-install-technique=ATECHNIQUE How to install addons: `linked' means the product or extension directory will be symlinked into the instance home, `tree-linked' means the directory structure will be re-created and then files symlinked, `copied' means the file will be copied into the instance home. Default: tree-linked. -r RESTART, --restart=RESTART when to restart on configuration of new products or extensions: `configuring' means after every product or extension configuration, `end' means at the end of the installation of all packages, `manually' means no automatic restart will happen. Default: end -u USER, --user=USER user and password for the initial user (in the form `user:password'); these settigs can be modified later using zpasswd.py utility from Zope. You'll be prompted for an username and password if the options is omitted. --service-user=SRVUSER system user used to run this instance (in the form `user:groupdefault'); this setting can be modified later editing the zope.conf file of the instance. Default: zope:zope --service-port=SRVPORT HTTP port used to run this instance; this setting can be modified later editing the zope.conf file of the instance. Default: 9673 --skelsrc=SKEL the directory from which skeleton files should be copied; must at least contain the following directories: `bin', `etc', `Extensions', `import', `lib', `log', `Products', `var' and files: `bin/zopeservice.py.in', `bin/run- zope.bat.in', `bin/runzope.in', `bin/runzope.in', `bin/zopectl.in', `etc/zope.conf.in'. Default: /usr/lib/zopeVER/skel remove-instance <instance> Remove an instance (except data files) and mark it as removed. purge-instance <instance> Purge files for an instance (including data files). show-instance <instance> Print a short summary about an instance. list-instances Print the list of available instances. instance-addon-mode <instance> [<mode>] Get or set an addon-mode for an instance. instance-addon-technique <instance> [<technique>] Get or set an addon-install-technique for an instance. instance-restart-policy <instance> [<restart-policy>] Get or set a policy on addon-installation for an instance. zopectl <instance> <zdctl-action> [<zdctl options>] Call a zopectl action (e.g. `start', `stop' or `restart') for a given instance. restart-pending-instances Restart instances with `restart-pending' markers. ACTIONS (ZEO instances handling) make-zeoinstance <instance> Create a new instance running Zope version specific mkzeoinstance. purge-zeoinstance <instance> Purge files for a ZEO instance (including data files). list-zeoinstances Print the list of available ZEO instances. zeoctl <instance> <zeotl-action> [<zeotl options>] Call a zeoctl action (e.g. `start', `stop' or `restart') for a given ZEO instance. ACTIONS (products and extensions handling) list-products, list-extensions show all products or extensions managed by dzhandle add-product, add-extension add a product or extension to an instance -l, --lazy Add missing addons only (error on manually installed addons). -t ATECHNIQUE, --addon-install-technique=ATECHNIQUE How to install the specified addons. remove-product, remove-extension remove a product or extension from an instance -l, --lazy Do not complain about already removed addons. -f, --force Force removal of the addons. ACTIONS (for Zope products maintainers) The following actions should be used inside the maintainer scripts of Debian/Ubuntu packages of Zope products and extensions. If the pack- age uses zope-debhelper's dh_installzope, these actions will be automatically included. dinstall-extension, dinstall-product install a packaged extension/product dremove-extension, dremove-product remove a packaged extension/product postinst-extension, postinst-product handle postinst of a packaged extension/product postrm-extension, postrm-product handle postrm of a packaged extension/product preinst-extension, preinst-product handle preinst of a packaged extension/product prerm-extension, prerm-product handle prerm of a packaged extension/product show-package-info show various information about zope packages SEE ALSO
dh_installzope(1), dh_installzopeinstance(1) AUTHOR
This manual page was written by Fabio Tranchitella <kobold@debian.org> for the Debian GNU/Linux and Ubuntu Linux systems (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts and no Back-Cover Texts. A copy of the license can be found under /usr/share/common-licenses/FDL. dzhandle(1)
All times are GMT -4. The time now is 08:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy