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 BSD

resolver

RESOLVER(5)							File Formats Manual						       RESOLVER(5)

NAME

       resolver - resolver configuration file

SYNOPSIS

       /etc/resolv.conf

DESCRIPTION

       The  resolver  configuration  file contains information that is read by the resolver routines the first time they are invoked by a process.
       The file is designed to be human readable and contains a list of name-value pairs that provide various types of resolver information.

       On a normally configured system this file should not be necessary.  The only name server to be queried will be on the local machine and the
       domain name is retrieved from the system.

       The different configuration options are:

       nameserver
	      followed by the Internet address (in dot notation) of a name server that the resolver should query.  At least one name server should
	      be listed.  Up to MAXNS (currently 3) name servers may be listed, in that case the resolver library queries tries them in the  order
	      listed.	If  no nameserver entries are present, the default is to use the name server on the local machine.  (The algorithm used is
	      to try a name server, and if the query times out, try the next, until out of name servers, then repeat trying all the  name  servers
	      until a maximum number of retries are made).

       domain followed	by  a domain name, that is the default domain to append to names that do not have a dot in them.  If no domain entries are
	      present, the domain returned by gethostname(2) is used (everything after the first `.').	Finally, if the host name does not contain
	      a domain part, the root domain is assumed.

       The  name  value  pair must appear on a single line, and the keyword (e.g. nameserver) must start the line.  The value follows the keyword,
       separated by white space.

FILES

       /etc/resolv.conf

SEE ALSO

       gethostbyname(3N), resolver(3), named(8)
       Name Server Operations Guide for BIND

4th Berkeley Distribution					September 14, 1987						       RESOLVER(5)