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
svc(8)							      System Manager's Manual							    svc(8)

NAME
svc - controls services monitored by supervise(8). SYNOPSIS
svc [ -udopchaitkx ] services DESCRIPTION
services consists of any number of arguments, each argument naming a directory used by supervise(8). svc applies all the options to each service in turn. OPTIONS
-u Up. If the service is not running, start it. If the service stops, restart it. -d Down. If the service is running, send it a TERM signal and then a CONT signal. After it stops, do not restart it. -o Once. If the service is not running, start it. Do not restart it if it stops. -p Pause. Send the service a STOP signal. -c Continue. Send the service a CONT signal. -h Hangup. Send the service a HUP signal. -a Alarm. Send the service an ALRM signal. -i Interrupt. Send the service an INT signal. -t Terminate. Send the service a TERM signal. -k Kill. Send the service a KILL signal. -x Exit. supervise(8) will exit as soon as the service is down. If you use this option on a stable system, you're doing something wrong; supervise(8) is designed to run forever. SEE ALSO
supervise(8), svok(8), svstat(8), svscanboot(8), svscan(8), readproctitle(8), fghack(8), pgrphack(8), multilog(8), tai64n(8), tai64nlo- cal(8), setuidgid(8), envuidgid(8), envdir(8), softlimit(8), setlock(8) http://cr.yp.to/daemontools.html svc(8)
All times are GMT -4. The time now is 08:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy