Building Linux cluster for mechanical engineering software Post: 302920299

Sponsored Content

Special Forums UNIX and Linux Applications High Performance Computing Building Linux cluster for mechanical engineering software Post 302920299 by DGPickett on Wednesday 8th of October 2014 03:18:17 PM

10-08-2014

Registered User

VNC on XWindows platforms creates a local virtual XWindow desktop that supports your choice of window managers, has low latency and can be viewed by a phelora of platform supporting viewers off your client machine of choice. I am using a JAVA viewer, as I lack local admin. The X tcp or unix sockets run inside the host for min laatency (unless you point off-host X clients to it), and a VNC socket connects the viewer. You can run the VNC tcp though an ssh tunnel for security.

Heterogenous clustering requires smarter load balancing and code compatability or porting. Java is portable, compared to C++/g++, which produces code specific to the CPU and O/S, but still is very widely available to compile locally compatible code.

VM makes sense. In practice, very few modern systems page much, and it makes the environment that much more robust. It can support huge sparse matrixes in an mmap()'d space, key to many problems.

Going highly parallel on cpu and ram suggest that net and file access will become bottlenecks, so yes, you need to put lots of work into making them as parallel as possible, too. Network fabric needs to be many path switches and high bandwidth. If you go fiber with either, remember that with its higher speeds comes higher latency, so problems may need to be structured to avoid that. Net and file have been becoming the same problem, as more and more file is remote from the host.

DGPickett

View Public Profile for DGPickett

Find all posts by DGPickett

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

building and running a software in different linux kernel versions

my Querry is if i build a software on a specific linux kernel and then try to run it on another linux kernel ....what can be the possible problems or what errors can most probably appear while running the binary in an updated version of linux.

2. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More...

3. High Performance Computing

Building a Linux Virtual Server cluster

Hi Guys, I'm busy building a LVS-NAT cluster on Red-Hat server 5.1 and I need a kernel that has LVS capabilities for a red-hat server 5.1. Is the anyone who can advise me where I can get this kernel. I have already visited the following site Ultra Monkey: and this has old kernels e.g. 2.4.20...

4. Red Hat

Free Cluster software with Red Hat Linux 5.0

Hi, I would like to know wheather any free cluster software is coming with Red Hat Ent Linux Medias? or needs to be purchased seperately.

LEARN ABOUT OPENSOLARIS

scds_syslog_debug

scds_syslog_debug(3HA)					 Sun Cluster HA and Data Services				    scds_syslog_debug(3HA)

NAME

       scds_syslog_debug - write a debugging message to the system log

SYNOPSIS

       cc [flags...] -I /usr/cluster/include file -L /usr/cluster/lib  -l  dsdev
       #include <rgm/libdsdev.h>

       void  scds_syslog_debug(int debug_level, constchar *format...

DESCRIPTION

       The  scds_syslog_debug() function writes a debugging message to the system log. It uses the facility returned by the scha_cluster_getlogfa-
       cility(3HA) function.

       All syslog messages are prefixed with: SC[<resourceTypeName>,<resourceGroupName>,<resourceName>,<methodName>

       If you specify a debug_level greater than the current debugging level being used, no information is written.

       The DSDL defines the maximum debugging level, SCDS_MAX_DEBUG_LEVEL, as 9. The scds_initialize(3HA) function, which the calling program must
       call before scds_syslog_debug(), retrieves the current debugging level from the file: /var/cluster/rgm/rt/<resourceTypeName>/loglevel.

       Caution -

	 Messages written to the system log are not internationalized.	Do not use gettext() or other message translation functions in conjunction
	 with this function.

PARAMETERS

       The following parameters are supported:

       debug_level	   Debugging level at which this message is to be written. Valid debugging levels are between 1 and  SCDS_MAX_DEBUG_LEVEL,
			   which  is  defined  as  9  by the DSDL. If the specified debugging level is greater than the debugging level set by the
			   calling program, the message is not written to the system log.

       format		   Message format string, as specified by printf(3C)

       ...		   Variables, indicated by the format parameter, as specified by printf(3C)

EXAMPLES

       Example 1 Display All Debugging Messages

       To see all debugging messages for resource type SUNW.iws, issue the following command on all nodes of your cluster

	 echo 9 > /var/cluster/rgm/rt/SUNW.iws/loglevel

       Example 2 Suppress Debugging Messages

       To suppress debugging messages for resource type SUNW.iws, issue the following command on all nodes of your cluster

	 echo 0 > /var/cluster/rgm/rt/SUNW.iws/loglevel

FILES

       /usr/cluster/include/rgm/libdsdev.h

	   Include file

       /usr/cluster/lib/libdsdev.so

	   Library

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWscdev 		   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Evolving			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       printf(3C), scds_syslog(3HA), scha_cluster_getlogfacility(3HA), syslog(3C), syslog.conf(4), attributes(5)

Sun Cluster 3.2 						    7 Sep 2007						    scds_syslog_debug(3HA)