Sponsored Content
Full Discussion: how to do GRID COMPUTING?
Special Forums UNIX and Linux Applications High Performance Computing how to do GRID COMPUTING? Post 302279505 by nsharath on Friday 23rd of January 2009 01:28:30 AM
Old 01-23-2009
Bug how to do GRID COMPUTING?

Hello,
I want to know how to combine the processing power of given 2 FEDORA machines in LAN.
Can you please tell me the commands,etc used to perform such an operations.Can you please give me the links where I can find more info on this topic.
 

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to create a grid file

Hi everybody: I want to create a grid file for export to statistical program. My aid is create a file with both rows, one row are x coordenates and other for y coordenates. All grid obviousolly are same space. the form that i want is this: x=(400000 ........ 600000) and y=(4000000 .......... (1 Reply)
Discussion started by: tonet
1 Replies

2. AIX

GRID containers technology

Hi forum, I am aware that on Hp-Superdome technology (Blade Servers) is avaliable while on Solaris GRID technology is the latest in the market. I would like to know if similar high end technology is also available for AIX ? (1 Reply)
Discussion started by: dheram
1 Replies

3. High Performance Computing

Grid vs. Parallel vs. Distributed

Hello all, I was wondering if someone could either explain or maybe point me to another article somewhere that explains the difference between: distributed computing grid computing parallel computing I see these terms thrown around a lot in server and cluster environments, but I'd like a... (2 Replies)
Discussion started by: Heathe_Kyle
2 Replies

4. Virtualization and Cloud Computing

Event Cloud Computing - IBM Turning Data Centers Into ?Computing Cloud?

Tim Bass Thu, 15 Nov 2007 23:55:07 +0000 *I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing... (0 Replies)
Discussion started by: Linux Bot
0 Replies

5. High Performance Computing

Alternative to Sun Grid Engine

Does anybody know of a good alternative to Sun Grid Engine? It seems that Oracle is now charging for this software. I am running a HPC cluster that has Solaris 10 machines and I am adding some nodes that will be running Ubuntu 10.04, eventually the Solaris machines will be migrating to Ubuntu. (0 Replies)
Discussion started by: ccj4467
0 Replies
TM::Bulk(3pm)						User Contributed Perl Documentation					     TM::Bulk(3pm)

NAME
TM::Bulk - Topic Maps, Bulk Retrieval Trait SYNOPSIS
my $tm = ..... # get a map from anywhere use TM::Bulk; use Class::Trait; Class::Trait->apply ($tm, 'TM::Bulk'); # give the map the trait # find out environment of topic my $vortex = $tm->vortex ('some-lid', { 'types' => [ 'types' ], 'instances' => [ 'instances*', 0, 20 ], 'topic' => [ 'topic' ], 'roles' => [ 'roles', 0, 10 ], 'members' => [ 'players' ], }, ); # find names of topics (optionally using a scope preference list) my $names = $tm->names ([ 'ccc', 'bbb', 'aaa' ], [ 's1', 's3', '*' ]); DESCRIPTION
Especially when you build user interfaces, you might need access to a lot of topic-related information. Instead of collecting this 'by foot' the following methods help you achieve this more effectively. names $name_hash_ref = $tm->names ($lid_list_ref, [ $scope_list_ref ] ) This method takes a list (reference) of topic ids and an optional list of scoping topic ids. For the former it will try to find the names (topic names for TMDM acolytes). If the list of scopes is empty then the preference is on the unconstrained scope. If no name for a topic is in that scope, some other will be used. If the list of scopes is non-empty, it directs to look first for a name in the first scoping topic, then second, and so on. If you want to have one name in any case, append "*" to the scoping list. If no name exist for a particular lid, then an "undef" is returned in the result hash. References to non-existing topics are ignored. The overall result is a hash (reference). The keys are of the form "topic-id @ scope-id" (without the blanks) and the name strings are the values. vortex $info = $tm->vortex (, $vortex_lid, $what_hashref, $scope_list_ref ) This method returns a lot of information about a particular toplet (vortex). The function expects the following parameters: lid: the lid of the toplet in question what: a hash reference describing the extent of the information (see below) scopes: a list (reference) to scopes (currently NOT honored) To control what exactly should be returned, the "what" hash reference can contain following components. All of them being tagged with <n,m> accept an additional pair of integer specify the range which should be returned. To ask for the first twenty, use "0,19", for the next "20,39". The order in which the identifiers is returned is undefined but stable over subsequent read-only calls. topic: fetches the toplet (which is only the subject locator, subject indicators information). names (<n,m>): fetches all names (as array reference triple [ type, scope, string value ]) occurrences (<n,m>): fetches all occurrences (as array reference triple [ type, scope, value ]) instances (<n,m>): fetches all toplets which are direct instances of the vortex (that is regarded as class here); instances* (<n,m>): same as "instances", but including all instances of subclasses of the vortex types (<n,m>): fetches all (direct) types of the vortex (that is regarded as instance here) types* (<n,m>): fetches all (direct and indirect) types of the vortex (that is regarded as instance here) subclasses (<n,m>): fetches all direct subclasses subclasses* (<n,m>): same as "subclasses", but creates reflexive, transitive closure superclasses (<n,m>): fetches all direct superclasses superclasses* (<n,m>): same as "superclasses", but creates reflexive, transitive closure roles (<n,m>): fetches all assertion ids where the vortex plays a role peers (<n,m>): fetches all topics which are also a direct instance of any of the (direct) types of this topic peers* (<n,m>): fetches all topics which are also a (direct or indirect) instances of any of the (direct) types of this topic peers** (<n,m>): fetches all topics which are also a (direct or indirect) instances of any of the (direct or indirect) types of this topic The function will determine all of the requested information and will prepare a hash reference storing each information into a hash component. Under which name this information is stored, the caller can determine with the hash above as the example shows: Example: $vortex = $tm->vortex ('some-lid', { 'types' => [ 'types' ], 'instances' => [ 'instances*', 0, 20 ], 'topic' => [ 'topic' ], 'roles' => [ 'roles', 0, 10 ], }, ); The method dies if "lid" does not identify a proper toplet. SEE ALSO
TM::Overview COPYRIGHT AND LICENSE
Copyright 200[3-57] by Robert Barta, <drrho@cpan.org> This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2008-04-23 TM::Bulk(3pm)
All times are GMT -4. The time now is 01:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy