Optimizing the system reliability Post: 32976

Sponsored Content

Special Forums Hardware Filesystems, Disks and Memory Optimizing the system reliability Post 32976 by Deepa on Wednesday 11th of December 2002 10:09:19 PM

12-11-2002

Registered User

Thanks Perderabo!

As you said, "Reliability will require duplicate servers, preferably in different cities", we do have a duplicate sun box geographically located in different cities, which has the same configuration and with the same number of processes running on it.

But the secondary machine is used only when the primary machine goes for a toss.

I am trying to find out the number of parallel instances of each process to be running in each machine, to attain a better reliability.

As u rightly said, we have to benchmark for gaining performance. I happened to hear about the genetic algorithm which can be applied for similar type of scenario. But still, we have to define the performance calculation of each process (considering the CPU load, memory usage, database accessing, IPC access etc) and provide it as one of the input to genetic algorithm.

I am not sure if any of our forum members are aware of this genetic algorithm(GA) concept. If anyone knows a good GA site/forum from where we can grab some information, pls let me know.

Thanks

Deepa

View Public Profile for Deepa

Find all posts by Deepa

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...

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...

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...

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...

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...

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...

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

LEARN ABOUT SUSE

starting

starting(7)						 Miscellaneous Information Manual					       starting(7)

NAME

       starting - event signalling that a job is starting

SYNOPSIS

       starting JOB=JOB INSTANCE=INSTANCE [ENV]...

DESCRIPTION

       The  starting  event is generated by the Upstart init(8) daemon when a new instance of a job begins starting.  The JOB environment variable
       contains the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs.

       init(8) will wait for all services started by this event to be running, all tasks started by this event	to  have  finished  and  all  jobs
       stopped by this event to be stopped before allowing the job to continue starting.

       This allows jobs to effectively insert themselves as dependencies of other jobs.  The event is typically combined with the stopped(7) event
       by services.

       Job configuration files may use the export stanza to export environment variables from their own environment into the starting event.   See
       init(5) for more details.

EXAMPLE

       A service that wishes to be running whenever another service would be running, started before and stopped after it, might use:

	      start on starting apache
	      stop on stopped apache

       A task that must be run before another task or service is started might use:

	      start on starting postgresql

SEE ALSO

       started(7) stopping(7) stopped(7) init(5)

Upstart 							    2009-07-09							       starting(7)