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
Old 10-08-2014
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.
 

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. (1 Reply)
Discussion started by: mobydick
1 Replies

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... (0 Replies)
Discussion started by: Linux Bot
0 Replies

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... (2 Replies)
Discussion started by: Linux Duke
2 Replies

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. (3 Replies)
Discussion started by: manoj.solaris
3 Replies
vncconfig(1)						     Virtual Network Computing						      vncconfig(1)

NAME
vncconfig - configure and control a VNC server SYNOPSIS
vncconfig [parameters] vncconfig [parameters] -connect host[:port] vncconfig [parameters] -disconnect vncconfig [parameters] [-set] Xvnc-param=value ... vncconfig [parameters] -list vncconfig [parameters] -get Xvnc-param vncconfig [parameters] -desc Xvnc-param DESCRIPTION
vncconfig is used to configure and control a running instance of Xvnc, or any other X server with the VNC extension. Note that it cannot be used to control VNC servers prior to version 4. When run with no options, it runs as a kind of "helper" application for Xvnc. Its main purpose when run in this mode is to support clip- board transfer to and from the VNC viewer(s). Note that without a running instance of vncconfig there will be no clipboard support. It puts up a window with some checkboxes which can be used to disable clipboard transfers if required (in the future there may be more func- tions available from this window). The -nowin flag can be used if you always want clipboard support but don't wish to clutter the desktop with this window - alternatively the -iconic option can be used to make it iconified by default. When run in any other mode, vncconfig is a one-shot program used to configure or control Xvnc as appropriate. It can be used to tell Xvnc to connect or disconnect from listening viewers, and to set and retrieve Xvnc's parameters. Note that the DISPLAY environment variable or the -display option must be set as appropriate to control Xvnc. If you run it on an ordinary X server (or on a version 3 Xvnc) you will get an error message saying that there is no VNC extension. OPTIONS
-connect host[:port] Tells an Xvnc server to make a "reverse" connection to a listening VNC viewer (normally connections are made the other way round - the viewer connects to the server). host is the host where the listening viewer is running. If it's not listening on the default port of 5500, you can specify host:port instead. -disconnect This causes Xvnc to disconnect from all viewers so that the VNC desktop is not displayed anywhere. [-set] Xvnc-param=value Sets an Xvnc parameter to the given value. Note that some of Xvnc's parameters are read only once at startup so that changing them in this way may not have any effect. -list Lists all the parameters supported by Xvnc. -get Xvnc-param Prints the current value of the given Xvnc parameter. -desc Xvnc-param Prints a short description of the given Xvnc parameter. PARAMETERS
vncconfig also has parameters of its own which can be set on the command line. These should not be confused with Xvnc's parameters which are manipulated with the -set, -get, -list and -desc options. Parameters can be turned on with -param or off with -param=0. Parameters which take a value can be specified as -param value. Other valid forms are param=value -param=value --param=value. Parameter names are case-insensitive. -display Xdisplay Specifies the Xvnc server to control. -nowin When run as a "helper" app, don't put up a window. -iconic When run as a "helper" app, make the window iconified at startup. SEE ALSO
vncpasswd(1), vncviewer(1), vncserver(1), Xvnc(1) http://www.realvnc.com AUTHOR
Tristan Richardson, RealVNC Ltd. VNC was originally developed by the RealVNC team while at Olivetti Research Ltd / AT&T Laboratories Cambridge. It is now being maintained by RealVNC Ltd. See http://www.realvnc.com for details. RealVNC Ltd 03 Mar 2005 vncconfig(1)
All times are GMT -4. The time now is 02:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy