Given by Geoffrey C. Fox at Beijing on 28 Dec 97 to 5 Jan 98. Foils prepared 8 January 98
Outside Index
Summary of Material
We discuss role of commodity (Web) technologies in future high performance computing environments |
We describe how a network of Web/CORBA/COM servers architecture can naturally support both parallel and distributed computing while |
We describe applications to both metacomputing, and parallel computing |
We suggest critical importance of CORBA and component based software in HPCC -- Javabeans seem very important |
We recommend agreement on standard interfaces or frameworks for computing and essentially seamless user interfaces |
We describe role of collaboration technology in linking computers with people |
We describe use of Java as a general coding language for scientific and engineering computation |
This approach unifies distributed event driven simulations with classic massively parallel time stepped computations |
Outside Index
Summary of Material
Geoffrey Fox |
Syracuse University |
NPAC |
111 College Place Syracuse NY 13244 4100 |
3154432163 |
We discuss role of commodity (Web) technologies in future high performance computing environments |
We describe how a network of Web/CORBA/COM servers architecture can naturally support both parallel and distributed computing while |
We describe applications to both metacomputing, and parallel computing |
We suggest critical importance of CORBA and component based software in HPCC -- Javabeans seem very important |
We recommend agreement on standard interfaces or frameworks for computing and essentially seamless user interfaces |
We describe role of collaboration technology in linking computers with people |
We describe use of Java as a general coding language for scientific and engineering computation |
This approach unifies distributed event driven simulations with classic massively parallel time stepped computations |
There are national HPCC programs in:
|
The USA activities include
|
Ideas from HPCC research Good! |
Not enough people/funding in field to implement robust production systems |
Must re-use as much software (including infrastructure software) as possible |
Similarly must build HPCC software in a modular fashion with small enough modules that smallish groups can build effectively |
Different modules are likely to use different base technologies (Fortran v Java v C++ etc.) and so interoperability essential! |
No silver bullet on the horizon - maybe pessimistic but implies better HPCC environments implies better implementations of existing ideas. |
Need to support both production use of MPP's and "rapid prototyping" in development of new applications - latter is not well supported by current HPCC software systems even though need parallel support for prototyping of new 3D simulations |
Some of current new developments focus on
|
Use of Commodity hardware: PC's offer best performance per dollar (Gigaflop for $30,000) |
Use of Commodity software: Windows NT, COM, CORBA, web, Java, VRML .... |
Use of Web to produce Seamless (universal) computer interfaces |
Java replacing C++ and Fortran for Numerical Computation |
Use of databases and collaboration technology to link people, databases and simulation |
Integration of parallel and distributed computing |
Use of distributed objects (CORBA) to encapsulated remote services |
Bottom of Pyramid has 1000 times dollar value and compute power of best supercomputer (tip of pyramid) but supercomputer has high performance network to support close synchronization needed by classic parallel algorithms |
Use of |
Web Technologies |
is naturally a |
16 Pentium Pro's in a cluster (cost $30K today) reach about 1 gigaflop on a tree code with 107 particles |
6800 Pentium Pro's (ASCI Sandia machine) with around 300 million particles
|
But tree code is 105 times as efficient as O(N2) code on this problem
|
The current incoherent but highly creative Web will merge with distributed object technology in a multi-tier client-server-service architecture with Java based combined Web-ORB's |
COM(Microsoft) and CORBA(world) are competing cross platform and language object technologies
|
Need to abstract entities (Web Pages, simulations) and services as objects with methods(interfaces) |
How do we do this while infrastructure still being designed! |
One can anticipate this by building systems in terms of Javabeans e.g. develop Web-based databases with Javabeans using standard JDBC (Java Database Connectivity) interfaces |
Design and Use Java Framework for Computing which will become a "CORBA facility"
|
From HPcc as High Performance Commodity Components |
There is a similar Java version of this using RMI and JDBC with of course the linked application being restricted to Java code. Corba and the analogous COM solution are cross-language solutions. |
From HPcc as High Performance Commodity Components |
Client Applet |
with JDBC and user (form) |
interface |
Oracle Database |
Java Socket |
Oracle Driver |
OCI |
Client with Applet Javabean |
Vendor Specific |
Object Broker |
Object |
Database |
IIOP |
Custom |
By definition, Object Web software is and will even more so, be the "best" software ever built because it has the largest market and greatest leverage of investment dollars
|
On should build upwards from the "democratic Web"
|
This allows you to both deliver your application to the general public (when required) and leverage best software |
Web, Object technologies and their linkage is still uncertain and there may be many changes but there are "enough" capabilities in place to build very general (essentially all?) applications
|
Field characterized by rapidly evolving standards and mechanisms to achieve rapid consensus |
Fortran77 --> Fortran90 --> HPF --> Fortran2000 -- 23 years |
VRML idea (1994) --> VRML1 deployed (95) --> VRML2 deployed (early 97) -- 2.3 years
|
Classic Web: HTTP MIME HTML CGI Perl etc. |
Java and JavaScript varying from compiled to almost compiled (applet) to fully interpreted Programming Language |
VRML2 as a dynamic 3D data structures for defining products and results of simulations |
Java Database Connectivity (JDBC) enables easy integration of databases into any system |
CORBA and COM maturing with Javabeans offering a visual (ComponentWare) object interface |
Dynamic Java Server and Clients |
Rich Web Collaboration Environment building electronic societies and linking people with computers |
Security model well understood and needs deployment of public key infrastructure |
Compression technology and Quality of Service for multimedia delivery also understood but again not generally deployed so the needed bandwidth (>= 100 kilobits) for reasonable video delivery is not generally available. |
1)One can "just" use Object Web technologies as a software infrastructure for building parallel, distributed or sequential computing environments which can have a very different architecture from the Web
|
2)Harness the power of the Web as a computer -- use up the idle cycles on the WebTV's in every home -- typically a Web Client based system
|
3)One can view the Object Web as a distributed information system with modest performance and build a metacomputing system with the Web architecture
|
So this is partly use of Object Web Software to build metacomputing systems of any architecture |
Perhaps VRML or Java3D are important for scientific visualization |
Web (including Java applets) front-ends provide convenient customizable interoperable user interfaces to HPCC facilities |
Perhaps the public key security and digital signature infrastructure being developed for electronic commerce, could enable more powerful approaches to secure HPCC systems |
Perhaps Java will become a common scientific programming language and so effort now devoted to Fortran and C++ tools needs to be extended or shifted to Java |
The universal adoption of JDBC (Java Database Connectivity) and the growing convenience of web-linked databases could imply a growing importance of systems that link large scale commercial databases with HPCC computing resources |
Javabeans, RMI, COM, CORBA, IIOP form the basis of the emerging "pragmatic object web" which analogously to the previous bullet could encourage a growing use of modern object technology which will allow better managed distributed systems |
Emerging collaboration and other distributed information systems could allow new (low end) distributed work paradigms which can be used in computational steering and for basic scientific research |
High end (today) to high end(tomorrow)
|
High end(today) to low end(tomorrow)
|
Low end(today) to low end(tomorrow)
|
Low end(today) to very low end (tomorrow)
|
The new application(s) we can't predict |
1997 |
2007 |
Larry Smarr and NCSA Collaboration have stressed analogy of deployment of computer/communication technology with impact that electrical and transportation grids had
|
The transportation system was built using lessons from and feed up/down from Sports cars, Cadillacs, Model T's, Ford Escorts etc. |
Computational Grid will be shaped by and shape all 5 classes of applications on previous foil
|
A highish end computational grid will in some sense (to be disagreed on) be influenced by and influence the "Object Web" which is here defined as "mass-market"/business IntraNet (low to low) use of Internet/distributed Information Systems |
Any large scale metacomputing/distributed computing environment will be shaped by and shape all 5 classes of applications on previous foil |
Even if only aimed at high end applications, the system will be influenced by and influence the "Object Web" or "commodity software infrastructure" which is here defined as "mass-market"/business IntraNet (low to low) use of Internet/distributed Information System |
Parallel Computing systems can be viewed as a special case of a Metacomputer
|
Applications are metaproblems with a mix of module and data parallelism |
Modules are decomposed into parts (data parallelism) and composed hierarchically into full applications.They can be the
|
Modules are "natural" message-parallel components of problem and tend to have less stringent latency and bandwidth requirements than those needed to link data-parallel components
|
Assume that primary goal of metacomputing system is to add to existing parallel computing environments, a higher level supporting module parallelism
|
We can distinguish Decomposition and Integration |
Decomposition is performed by an HPF or other Parallelizing compiler; or by a user writing a Fortran + Message Passing code "by hand" |
MPI integrates decomposed parts together with high bandwidth latency constraints |
Systems such as AVS integrate larger modules together and much of "software engineering" (modular style of programming) involved with this |
Web is a powerful integration model suitable for large coarse modules with modest latency and sometimes modest bandwidth requirements
|
Collaboration, computational steering, multidisciplinary science are all integration and not decomposition problems! |
Object Web Software provides a high functionality but modest performance distributed computing (Metacomputing) environment based on either Web (soon to be CORBA IIOP and HTTP/Java Socket) Servers or Clients |
Here we will explore an architecture using servers for control as higher functionality than clients although currently less broadly deployed
|
Object Web Only addresses Integration of already decomposed parts!
|
Middle Tier |
Basic Web Server |
Custom Web Server |
TP Server |
Business Transaction Management |
You Write Software |
at Client and Server |
Old and New Useful Backend Software |
1:User View: Interoperable Web Interface accessing services through Java Compute Services Framework |
2:Network of Java Servers provide distributed services with databases, compute engines, collaboratories, object brokers, instruments
|
Back end "Number Crunchers" linked either by communication at level 2 (slowish but easy) or at level 3 (high performance but more work) |
Compute processes linked either to servers or together by MPI if parallel |
Java Servers |
We have a set of Services hosted by Object Web Servers which form the middleware and accessed by clients |
Groups of clients (electronic societies) are linked by Java server based collaboration systems such as TANGO or Habanero |
Access |
Resources |
Store |
Multimedia Information |
Collaboration Server |
File Systems |
and/or Database |
Object Broker |
Database |
Simulation |
e.g. NEOS |
Netsolve |
Computer |
Person2 |
Shared |
WhiteBoard |
Shared Client Appl |
Person1 |
General User |
Systems like Tango or Habanero built around Java Servers integrate a group of multiple clients as a "Service" at the middle Java Server level |
Building systems in this way automatically includes "people in the loop" -- Computational Steering, Education, Multidisciplinary collaborative design |
Group of collaborating clients |
and client applications |
Database |
Object Broker |
MPP |
Here are some examples of using our approach where large scale industry investment in Web technology appears to add significant value to metacomputing systems built with Web architecture
|
Multidisciplinary and Computational Steering Applications
|
Visual and Interpreted Programming Environments
|
Technologies to get High Performance CORBA |
Integration with Forces Modeling (Distributed Event driven Simulation) |
Integration with Networked enabled servers such as NEOS and Netsolve
|
HTTP (Hyper Text Transport Mechanism)
|
Web Client
|
Web Servers
|
WorkFlow |
ORB |
System Management |
HPcc ? |
.............. |
Trader |
Security |
.......... |
Naming |
Persistence |
Oil & Gas |
DMSO Modeling and Simulation |
Imagery |
Banking |
Manufacturing |
...... |
...... |
Services |
Horizontal Facilities |
Vertical |
Facilities |
Standard Interfaces |
i.e. Frameworks |
OMG (Object Management Group)
|
ORB (Object Request Broker)
|
IIOP (Internet Inter Orb Protocol)
|
CORBA (Common Object Request Broker Architecture)
|
COM (Common Object Model)
|
ComponentWare
|
Object Web
|
JDBC (Java Data Base Connection)
|
Javabean
|
RMI (Remote Method Invocation)
|
HPCC (High Performance Computing and Communication)
|
Computational Grid
|
HPcc (High Performance commodity computing)
|
Java for the User Interface: This is roughly the "WebWindows Philosophy" of building applications to Web Server/Client Standards |
Java for Coarse Grain Software Integration: see collaboration and metacomputing |
Java as a high performance scientific language: for "inner" (and outer) loops Here parallelism is important but sequential issues also critical and first issues to examine! |
This is least controversial and is essentially WebWindows for User Interfaces |
Fortran was never good at user interfaces! |
Initially Aimed at education where usability higher priority than performance |
Teaching Java and JavaScript greatly aided by interpreted technology which allow integration of demonstrations into lectures |
VPL aimed at allowing embedding of F90, HPF and MPI (etc.) examples in lectures and convenient support of homeworks for transient inexperienced users. |
Features of VPL:
|
One example is VPL -- Virtual Programming Laboratory -- interface to HPF and MPI used by Syracuse and Cornell in courses/training |
If you agree that it can be web based then naturally Implemented as Java Framework for Computing Services |
Any Job |
Computer A |
Computer B |
Computer C |
Universal Interface |
Click on SnapShots in Virtual Programming Lab |
From NIST Sp2 Web Interface by Robert Lipman http://www.nist.gov/itl/div887/sasg/websubmit/ |
From NIST Sp2 Web Interface by Robert Lipman htt/www.nist.gov/itl/div887/sasg/websubmit/ |
Scivis is a client-server (3-tier) data visualization and analysis system by taking full advantage of Java. |
The purpose of this system is provide researchers with a customizable data analysis system to aid their research. |
We also provide a collaborative framework, where the users can exchange data and their own personalized filters. |
Available via http://kopernik.npac.syr.edu:8888/scivis |
Contains over 29K lines of Java code (2K lines of user-definable filters). |
A screen dump from a Scivis Session |
VRML naturally gives 3D visualization with usual Web advantage of running on PC's and Workstations |
Its universality implies can use in industry to specify products so can design, manufacture and market from the same(related) specification |
Should impact PDES/STEP and such industry product specification standards |
VRML will need extension to handle this but it is a good start and allows user defined types |
VRML and Parallel Computing?
|
NPAC Web Based Geographical Information System in Stand Alone Mode |
A GIS application is a specialized OpenInventor viewer, however it accepts any OpenInventor 2.1 scene model. That's why it's so easy to integrate it with third party applications, which produce IO/VRML output. The images show GIS integration with Weather Simulation application. A GIS viewer can also display animated objects controlled by Simulation Engine. |
It is natural to base on either a network of Web Clients or Web Servers
|
Web Client Models Include SuperWeb (Javelin) from UCSB and are well illustrated by the January 1997 hotwired article "Suck your Mips". |
Greater functionality but less power and pervasiveness is a pure Web Server model as proposed by NPAC
|
Note total compute power in all Web "clients" is about 100 times that in all Central Supercomputers |
http://www.packet.com/packet/ Hot Wired Tuesday January 7 Edition |
Applet calculates pi while you read article! |
1:User View: Interoperable Web Interface accessing services through Java Compute Services Framework |
2:Network of Java Servers provide distributed services with databases, compute engines, collaboratories, object brokers, instruments
|
Back end "Number Crunchers" linked either by communication at level 2 (slowish but easy) or at level 3 (high performance but more work) |
Compute processes linked either to servers or together by MPI if parallel |
Java Servers |
This is "middleware" which is implemented in simplest form as a network of Java Servers
|
Access |
Resources |
Store |
Multimedia Information |
Collaboration Server |
File Systems |
and/or Database |
Object Broker |
Database |
Simulation (Network-enabled |
servers such as NEOS, Netsolve) |
Sequential |
or Parallel |
Computer |
As a first step, implement multi-module systems with each module linked via Java Servers
|
Where necessary "escape" down to classic HPCC technologies for data transport keeping control at server level
|
This seems very convenient in JDK 1.1 "event model" which is mechanism used by Javabeans to communicate
|
1)Simple Server Approach 2)Classic HPCC Approach |
3)Hybrid Approach with control at server and |
data transfer at |
HPCC level |
4)Invoke High Performance Message Transfer between Observers and Sources specified in Message Event |
Server Tier |
Data Source |
Data Sink (Observers) |
5)Actual Data Transfer |
High Performance Tier |
2)Prepare |
Message Event in Source Control |
1)Register Observers with Listener |
Here are some examples of using our approach where large scale industry investment in Web technology appears to add significant value to metacomputing systems built with Web architecture
|
Multidisciplinary and Computational Steering Applications
|
Visual and Interpreted Programming Environments
|
Technologies to get High Performance CORBA |
Integration with Forces Modeling (Distributed Event driven Simulation) |
Integration with Networked enabled servers such as NEOS and Netsolve
|
Note Java also integrates compiled and interpreted approaches and so leads to more convenient programming environments
|
JavaScript is a fully interpreted language but not really Java |
Applets are half-way between traditional compiled and interpreted approaches |
Web "systems" can behave like Interpreters with interactive commands at client (gives Web version of MATLAB) |
Web Client |
including |
Java Applets |
Web Server |
Java/Fortran/C++ |
Application Backend |
User Interpreted Commands |
invoking preloaded |
Java/Javascript objects |
Server invokes extrinsic |
processor |
(true interpreter |
or compiler invoked |
dynamically) |
Running Program |
interruptable at |
extrinsic interfaces |
Compiler offers:
|
Interpreter offers:
|
JAVA applet |
HTTP |
server |
HPF |
server |
Node 1 |
Node 2 |
Node 3 |
Node 4 |
Node 5 |
Node 6 |
Web Browser |
Server Host |
1. Contact HTTP server to download the Java applet |
2. Use the applet to start instrumented HPF application |
3. HPF server starts (implemented as an HPF extrinsic) |
4. Java applet establishes communication with the HPF server |
5. HPF server accepts user's requests: |
- suspend/resume execution of the HPF code |
- send data |
- interpret new HPF statements |
- dynamically link and execute shared objects |
HPF statements and Visualization requests in Java, HPF etc. |
HPF extrinsic procedure |
Shared Object |
Lexical Analysis: PCRC frontend. |
HPF compilation: pghpf |
Pool of shared objects |
HPF RTS |
HPF |
server |
Dynamical linking |
Instrumented HPF |
JAVA |
applet |
Simulation |
Basic Display |
Image Filter |
is another |
module |
Output Display after Filter |
Runs as a |
parallel |
module |
using |
Java Server |
host |
Bunch of Filters and Displays |
defined in |
Java Graph editor and |
running on grid of Java Servers |
Original Image |
Visual Basic/C++/J++ and ActiveX or Beanboxes with Javabeans give visual approach to software objects
|
Enterprise Javabeans and COM are extending this to distributed computing |
Using Web technologies for grid and building modules out of (whatever Javabeans/COM evolves to) allows one to deliver to user HPCC programming environments with comparable friendliness to those in PC world |
They are Java's implementation of "component-based" visual programming |
This modern software engineering technique produces a new approach to libraries which become a "software component infrastructure(SCI)" |
There is a visual interface to discovery of and setting of values of and information about parameters used in a particular software component |
JavaBeans uses the event model of JDK1.1 to communicate between components
|
The visual interface allows inspection of and implementation of both individual beans and their linkage . This visual construction of linkage allows one to form nontrivial programs with multiple communicating components |
Apart from the event mechanism which is a communication/linkage mechanism, ComponentWare (and JavaBeans in particular) "just" give a set of universal rules (needed for interoperability) for rather uncontroversial (albeit good) object-oriented and visual programming practices
|
In general it is any process, but it is convenient (in the pure form of our web approach) to view each module as a Javabean (or equivalent component) |
The Javabean can wrap existing Fortran, Perl or C C++ code by either using native methods or by invoking the code as a separate process |
Modules as Javabeans allow them to be stored as objects and inspected visually
|
Wrapping existing code as Javabeans is a good way of renovating "legacy code" so can be used more easily in future!
|
Large gains in HPCC user productivity will be attained if we can integrate the ideas and technologies of modern (PC) visual programming with classical HPCC approaches |
Use of important emerging Web and CORBA technology allows HPCC object (C++.,Java) and visual (CODE, Hence, WebFlow, AVS, Khoros) systems to be enhanced to become parallel component-based visual programming systems. |
CORBA does not incorporate HPCC but as it specifies services and not implementation,
|
HP-CORBA can be built on Nexus and Globus and it will allow HPCC users access to any CORBA service with an option for high performance when necessary. |
The NPAC WebFlow technology can be combined with emerging JavaBean technology to produce a prototype HPcomponent system. |
Note industry is ahead with sequential ComponentWare but is only now moving with activeX to distributed systems. HPCC already has visual distributed environments. So HPCC need not be behind if it generalizes modules to Javabeans |
We present the proposed process of integrating HPCC and Enterprise Computing technologies on 2-dimensional 3x3 chart, exposing the evolution of user and system perspectives on new computing technologies. |
On the (vertical) system/complexity axis, we start from PC desktop and we evolve towards distributed and finally HPCC computing. |
On the (horizontal) user/simplicity axis, we start from objects and we evolve towards reusable components and finally their visual development and runtime environments. |
The first row on our char represents the already established PC technologies exemplified by systems such as Visual C++/J++, VBScript, Borland Delphi, Visual Cafe etc. |
The second row corresponds to the emergent Object Web based Enterprise Computing that integrates Java/JavaBeans based component technologies with CORBA based distributed objects. |
Finally, the third row represents our proposed HPCC extensions of these technologies in terms of HP-CORBA based HP-Components. |
The "Host" is logically a separate Corba object but could of course be instantiated on the same computer as one or more of the nodes. Using the protocol bridge of fig. 15, one could address objects using Corba with local parallel computing nodes invoking MPI and remote accesses using Corba where its functionality (access to very many services) is valuable. |
From HPcc as High Performance Commodity Components |
This allows MPI (or equivalently Nexus, Globus or PVM) and commodity technologies to coexist with a seamless user interface. |
From HPcc as High Performance Commodity Components |
From HPcc as High Performance Commodity Components |
The "Host" is logically a separate Corba object but could of course be instantiated on the same computer as one or more of the nodes. Using the protocol bridge of fig. 15, one could address objects using Corba with local parallel computing nodes invoking MPI and remote accesses using Corba where its functionality (access to very many services) is valuable. |
From HPcc as High Performance Commodity Components |
At present, JavaBeans technology is focused on component programming within a single Java VM. |
Within the Sun philosophy of '100% Java', distributed Beans can be developed using RMI interconnect. However, the rest of the industry tries to protect their C++ investments while converting to Java. |
Hence, in parallel with JavaBeans development, the Web industry explores now the linkage of Java with CORBA based distributed object technologies which offer an full C++/Java interoperability. |
CORBA supports cross-language remote object invocation as well as IIOP (Internet Inter-ORB Protocol) based interoperability between object brokers from various vendors. |
Of particular interest are Java based ORBs or ORBlets which can be downloaded as applets to enable CORBA capabilities also at the client/browser side. |
An alternative, offered by Netscape, is a resident ORB support in all browser and server products. |
Java based ORBs will soon turn the Web, so far acting as a largely passive document publishing framework, into a powerful dynamic world-wide distributed object-based computing environment. |
Now consider how to make the Object Web High performance. |
In the object domain we propose the extension HP-CORBA of the CORBA model for the HPCC domain by developing a minimal high performance ORB on top of MPI/Nexus. |
Such HP-ORBlets, residing in the individual nodes of a parallel system (either as network daemons or as runtime libraries) would allow one to hide explicit message passing calls in terms of higher level more user-friendly remote object invocations.
|
HP-ORBlets would focus on high performance data/method communication support, whereas the lower bandwidth control communication would be passed to and handled by the full functionality lower performance commercial ORBs in the CORBA bus in the middleware layer. |
The split between data and control communication would be fully transparent at the program's level, i.e. both parallel object developers and integrators would be offered a uniform CORBA object based programming model.
|
Two major advantages of the proposed approach are:
|
A large number of new Java APIs for advanced Web Services are emerging from JavaSoft and partners. Many current problems such as with the NPS WebDIS networking will be soon solved in a more robust, stable and elegant fashion by the new high-level APIs. |
Java APIs are organized in Java Frameworks. Current list of frameworks include:
|
Java Security Framework - support for authentication encryption, digital signatures. |
Java Commerce Framework - Java Wallet, Java Cassettes (digital credit cards). |
Java Beans Framework - componentware API with support for GUI negotiation and merging, persistence (JAR files), event filtering, introspection, visual application builders |
Java Media Framework - Java2D (with Adobe), animation (with Macromedia), audio/video (with Intel), Java3D (with SGI), JSDA (Java Shared Data API). |
All APIs listed are either already operational within JDK1.1, or still in works (spec only or alpha or beta release) but with the final release dates in 1997. |
Numerical Computing Framework
|
Computing Services Framework
|
High Performance Framework
|
Distributed Computing Framework
|
Distributed Simulation Framework
|
Java Calls (mainly Interfaces and not methods) to capabilities expressed in implementation neutral form |
Drivers convert these general calls to vendor specific implementation of service |
Java code can either be all on client (2-tier) or on client and middle tier (3 tier) |
e.g. JDBC is a universal interface to all relational databases |
Adoption of this JDBC implies that vendor specific solutions (such as Oracle's PL/SQL) are immediately less attractive
|
Note database business is larger than simulation business
|
These are too many suggested computing frameworks and probably several are rather controversial as there is no agreed model of the use of Java in Computing
|
The most promising for early consideration are |
1) The Numerical Computing Framework which is essentially use of Java in Computational Science and Engineering |
Very important to get agreement on areas that affect JavaVM and the Java Language as these are getting harder to change
|
2) The Computing Services Framework which we give more detail on. |
Enables development of Web Interfaces to run a given job on any computer compliant with this framework just as JDBC gives a universal interface to any relational database
|
The Computing Services Framework allows vendors to compete on either User Front End (GUI) or back end services with the JavaCS framework providing universal linkage |
The framework is implemented at the backend as a set of drivers which map generic Java Interfaces to particular software (e.g. a compiler) on particular machines. |
Requires agreement by "suitable interested parties" on
|
http://www.sis.port.ac.uk/~mab/Computing-FrameWork/ |
Is CORBA (viewing system as a collection of objects) useful |
Compiling, Executing, Specification of features needed for execution optimization
|
Accounting -- use Web commerce technology? |
Security (especially hard in metacomputing as link several different management policies)
|
Sharing, Accessing and Storing into File Systems |
Data and Performance Visualization Interface (how applets access server side information) |
Performance measurement and recording (cf: Pablo SDDF) |
Interfaces for Programming Tools
|
Libraries including names in Math class and
|
Module linkage model for metaproblems (multidisciplinary applications) as in Javabeans sufficient? |
DoD modeling community is currently evolving towards the HLA(High level Architecture) framework with the RTI (Run Time Infrastructure) based communication bus. |
The goal of HLA/RTI is to enhance interoperability across more diverse simulators than in the DIS realm, ranging from real-time to time-stepped to event-driven paradigms. |
HLA defines a set of rules governing how simulators (federates) interact with each others. Federates describe their objects via Object Model Template (OMT) and agree on a common Federation Object Model (FOM). |
The overall HLA/RTI model is strongly influenced by the CORBA architecture and in fact the current prototype development is indeed CORBA based. |
We suggest that next step is to combine CORBA2 (Initial HLA/RTI is CORBA1) with NPS prototype ideas to give a fully object and Web integrated event driven simulation environment. |
Java3D is natural visualization environment in this scenario |
Defense Modeling & Simulation Office |
(703) 998-0660 Fax (703) 998-0667 hla@msis.dmso.mil |
http://www.dmso.mil/ |
Comments in Green with a left vertical bar |
have been added by NPAC |
and are not endorsed by DMSO |
Original Powerpoint at http://www.dmso.mil/hla/edu_trng/regional/core_mat/ |
This selection at http://www.npac.syr.edu/users/gcf/dmsohlaforarldec97/ |
See also http://osprey7.npac.syr.edu:1998/iwt98/projects/webhla/ |
88 89 90 91 92 93 94 95 96 |
Technical |
Management |
Limited scope simulations, little interoperability prior to 1988 |
DSB: Computer Applications |
to Training & Wargaming |
DIS Standards begun |
ALSP- linking of Service wargames |
DEPSECDEF Memo |
EXCIMS and DMSO established |
SIMNET |
HLA Baseline approved |
HLA begun |
Service M&S Offices established |
DoDD 5000.59 |
Federation: a set of simulations, a common federation object model, and supporting RTI, that are used together to form a larger model or simulation |
Federate: a member of a federation; one simulation
|
A federate could be large or small grain -- for initial activity of integrating existing pre HLA simulations, a federate is typically large grain size |
However HLA is a "complete" model and one could build simulations where a federate is finr grain object and federation is simulation of these interacting objects |
Federation Execution: a session of a federation executing together |
Object: An entity in the domain being simulated by a federation that
|
Interaction: a non-persistent, time-tagged event generated by one federate and received by others (through RTI) |
Attribute: A named datum (defined in Federation Object Model) associated with each instance of a class of objects |
Parameter: A named datum (defined in Federation Object Model) associated with each instance of a class of interactions |
HLA Rules: A set of rules which must be followed to achieve proper interaction of federates during a federation execution. These describe the responsibilities of federates and of the runtime infrastructure in HLA federations
|
Interface Specification: Definition of the interface services between the runtime infrastructure and the federates subject to the HLA
|
Object Model Templates: The prescribed common method for recording the information contained in the required HLA Object Model for each federation and federate
|
1. Federations shall have an HLA Federation Object Model (FOM), documented in accordance with the HLA Object Model Template (OMT) |
A FOM is like a particular facility in CORBA |
2. In a federation, all representation of objects in the FOM shall be in the federates, not in the runtime infrastructure (RTI) |
3. During a federation execution, all exchange of FOM data among federates shall occur via the RTI |
4. During a federation execution, federates shall interact with the runtime infrastructure (RTI) in accordance with the HLA interface specification |
5. During a federation execution, an attribute of an instance of an object shall be owned by only one federate at any given time |
6. Federates shall have an HLA Simulation Object Model (SOM), documented in accordance with the HLA Object Model Template (OMT) |
7. Federates shall be able to update and/or reflect any attributes of objects in their SOM and send and/or receive SOM object interactions externally, as specified in their SOM |
8. Federates shall be able to transfer and/or accept ownership of attributes dynamically during a federation execution, as specified in their SOM |
9. Federates shall be able to vary the conditions (e.g., thresholds) under which they provide updates of attributes of objects, as specified in their SOM |
10. Federates shall be able to manage local time in a way which will allow them to coordinate data exchange with other members of a federation |
Object Class Structure Table |
Object Interaction Table
|
Attribute/Parameter Table
|
FOM/SOM Lexicon
|
General Case |
Example |
P=Publish and S=Subscribe |
General Case |
Example |
Live |
Participants |
Interface |
Runtime Infrastructure |
Data Collector/ |
Passive Viewer |
Federation Management Declaration Management |
Object Management Ownership Management |
Time Management Data Distribution Management |
RTI is a bit like IIOP with critical addition of time |
management services |
A large number of new Java APIs for advanced Web Services are emerging from JavaSoft and partners. Many current problems such as with the NPS WebDIS networking will be soon solved in a more robust, stable and elegant fashion by the new high-level APIs. |
Java APIs are organized in Java Frameworks. Current list of frameworks include:
|
Java Security Framework - support for authentication encryption, digital signatures. |
Java Commerce Framework - Java Wallet, Java Cassettes (digital credit cards). |
Java Beans Framework - componentware API with support for GUI negotiation and merging, persistence (JAR files), event filtering, introspection, visual application builders |
Java Media Framework - Java2D (with Adobe), animation (with Macromedia), audio/video (with Intel), Java3D (with SGI), JSDA (Java Shared Data API). |
All APIs listed are either already operational within JDK1.1, or still in works (spec only or alpha or beta release) but with the final release dates in 1997. |
Numerical Computing Framework
|
Distributed Simulation Framework
|
Computing Services Framework
|
High Performance Framework
|
Distributed Computing Framework
|
Enables development of Web Interfaces to run a given job on any computer compliant with this framework just as JDBC gives a universal interface to any relational database |
Compiling, Executing |
Scheduling jobs as in Codine or LSF |
Accessing and storing into File Systems |
Visualization Interface (how applets access server side information) |
The Computing Services Framework allows vendors to compete on User Front End (GUI) or back end services |
The framework is implemented as a set of drivers which map generic Java Interfaces to particular software (e.g. a compiler) on particular machines. |
Although we have 384 foilsets imported to the Web -- this is not the correct way of doing it!
|
Originally we thought a "Web Foil" is an enhanced HTML and we built a prototype using HotJava |
However now believe this is not powerful and correct Web implementation of "foils" is a JavaBean stored as a serialized Java Object
|
Start with a full drawing program supporting "art" and importing of images where basic entities are Java objects |
Start with system integrated with Tango |
Basic Unit is a "foil" -- typically NOT scrolled (but supporting this) |
Foils are arranged into foilsets dynamically as in current WebWisdom and allow notes(addons) etc. |
Import existing PowerPoint/Persuasion from "outline" text with automatic font size scaling
|
Allow user to add highlighting and images "cut" from original screendump of PC foil |
Latest Tango Capabilities June 97 |
An Applet based system using LiveConnect and plugin with Netscape3 and Signed Applets with Netscape4 |
Supports general shared event model of collaboration where it can share applications in Java, JavaScript, C, VRML, C++ (Open Inventor)
|
Has conventional general tools
|
Developed for command and control |
Most extensively used in education -- especially for course between Syracuse and Jackson State
|
Java is basis of Web Collaboration Systems with Applets Coordinated by Java Server |
Habanero from NCSA was one of first |
TANGOsim uses more modern Web Technology and incorporates a Discrete Event Simulator |
TANGO is a software framework supporting computer-based communication and collaboration
|
TANGO supports client side electronic societies of people, instruments and their applications. |
TANGO links these to a network of Java Servers which manage TANGO sessions and interfaces them to the world wide Server Infrastructure that underlies our model of Web applications
|
Electronic societies or groups are managed by core database in TANGO |
Systems like Tango or Habanero built around Java Servers integrate a group of multiple clients as a "Service" at the middle Java Server level |
Group of collaborating clients |
and client applications |
Database |
Object Broker |
MPP |
Technically, TANGO is a distributed system based on event broadcasting
|
Core system is implemented in Java and as a browser plug-in |
Base programming module is a Java applet
|
From Tango - A Java/WWW-Based Internet Collaborative Software System part of NPAC Overview May 1997 |
From Tango - A Java/WWW-Based Internet Collaborative Software System part of NPAC Overview May 1997 |
Global architecture is a mesh of servers
|
Session metaphor is a meeting room with tools
|
Asynchronous collaboration is (will be) enabled via session recording to database backend |
TANGO modules can be downloaded from anywhere
|
Application select |
buttons |
Application |
Domains |
Open/close and |
floor control |
Session |
information |
User information |
TANGO session, sync, and |
floor control buttons built |
into the application control |
panel. |
Generic tools: chats (1D, 2D, 3D*), whiteboards (paint and draw) |
Multimedia tools: audio/video conferencing, collaborative indexed streaming video |
Shared browsers: slide shows, fully synchronized, shared JavaScript, customizable client-side apps |
Virtual University: WebWisdom - interactive contents delivery system, a set of applets for physics curriculum |
Domain specific applets: 2D and 3D (collaborative VRML) Visible Human, collaborative AutoCad (feasibility study only) |
Core system implemented by a team of 3 programmers within ~6 months, available.
|
APIs for Java, C/C++, and JavaScript available |
Two generations of GUI implemented |
"Lessons learned" are being incorporated into TANGO II, scheduled for release end of October
|
Basic architectures
|
Basic architectures
|
Sharing possible only if applications deterministic
|
Copies of applications must be present everywhere
|
Environments must be identical
|
Initial state of a newcomer impossible to define
|
Cannot maintain consistency among copies
|
The pros win! Web model enables event broadcasting! |
TANGOsim |
Basic |
Replicated Applications |
1)Virtual Users 2)Customized Views |
TANGO Java |
Collaboratory |
Server |
HTTP |
Server |
MultiMedia Mail |
C2 Commander |
Chat |
VTC |
Event Driven |
Simulation |
Engine |
C2 Radar Officer |
3D GIS |
Scripting |
Language |
C2 Weather Officer |
Message Routing |
SW/Data Distrib. |
Other |
Collaborators |
MultiMedia Mail |
Chat |
Simulation |
Engine Controller |
All Clients |
Typical Clients |
Feb 97 Demonstration of Tango |
From Tango Project for CEWES Collaborative Tool Meeting |
TANGO links people and shared applications such as chat board, audio video conferencing, visualizations, shared white board, common AUTOCAD design and related tools |
CFD |
TANGO Server |
Database |
Object Broker |
MPP |
Structures |
MPP |
Engineer |
+ core |
services |
Visualization e.g.CAVE |
Shared AutoCAD |
Engineer |
+ core |
services |
This combines TANGO for collaboration with WebFlow to link server side applications |
If necessary WebFlow would support high performance inter-module communication as in structures-CFD Linkage example but it would always implement control and this allows TANGO integration with server side computation
|
WebFlow communication model is a dynamic dataflow |
Of course other server side compute models are possible and in general need (web-linked) data bases, file systems, object brokers etc., |
WebFlow supports dataflow model where user must supply routines to process input of data that drives module and output of data for other modules |
TANGO supports shared state and user supplies routines that read or write either
|
Can be done for applications like AUTOCAD as vendor supplies necessary API |
CFD |
Structures |
We have a set of Services hosted by Web Servers and accessed by clients |
Groups of clients (electronic societies) are linked by collaboration systems such as TANGO |
Access |
Resources |
Store |
Multimedia Information |
TANGO Server |
File Systems |
and/or Database |
Object Broker |
Database |
Simulation |
Computer |
Person2 |
Shared |
WhiteBoard |
Shared Client Appl |
Person1 |
General User |
Clearly Java Collaboration Systems are natural implementations of general environments that mix computers and people |
Computational Steering -- a simulation is like a participant in a Tango session which has
|
Need to link to Tango, Java data analysis/visulaization front ends as well as distributed resource management systems such as ARMS from Cornell |
Note synergy with Java Server based distributed computing such as WebFlow which builds an AVS like environment with graphical interfaces to software Integration |
More ambitious to upgrade discrete event simulation component of TANGOsim to support full SIMNET/DSI (Distributed Simulation Internet) functionality. |
Note that Java is natural language for DSI/Forces Modelling because these typically use object parallelism which fits both language and applet/JavaBean capabilities. |
See discussion in http://www.npac.syr.edu/projects/javaforcse |
Participants at JSU |
Teacher/Lecturer at NPAC |
Education applications include "classic guided tour" and more interestingly shared simulations
|
Delivering "consulting" version to DoD (CEWES)
|
Need to make even more robust/"user error proof" |
More sophisticated multi-room customizable version under development |
Develop database backend for logging of sessions |
Java for User Interfaces and MetaComputing is natural from its design! |
Java for your favourite Conjugate Gradient routine (etc.) is less obvious ..... |
Java likely to be a dominant language as will be learnt and used by a broad group of users
|
Java may replace C++ as major system building language
|
Clearly Java can easily replace Fortran as a Scientific Computing Language as can be compiled as efficiently and has much better software engineering (object) and graphics (web) capabilities
|
Java can unify classic science and engineering computations with more qualitative macroscopic "distributed simulation and modelling" arena which is critical in military and to some extent industry |
Key question is performance of Java |
Note Web Software can be run on High Performance IntraNets such as Iway so hardware need NOT be a problem! |
Java is currently semi-interpreted and (as in Linpack online benchmark) is about 50 times slower than good C or Fortran
|
Java --> (javac)--> Downloadable Universal Bytecodes --> (Java Interpreter) |
--> Native Machine Code
|
However Language can be efficiently compiled with "native compilers" |
Java ----> (native compiler) |
---> Native (for Particular Machine) Code |
Lots of Interesting Compiler issues for both compiled and scripted Java |
My SGI INDY gets .54 Megaflops for Java 100 by 100 Linpack |
It has 200 Mhz R4400 and current Netlib benchmark for this chip is 32 mflops for optimized Fortran |
For better resolution see JPEG Version |
see http://www.netlib.org/benchmark/linpackjava/ |
Note Just in Time Compilers are giving a factor of 10 from June 96 Measurements! |
see http://www.netlib.org/benchmark/linpackjava/ |
Syracuse and Las Vegas Workshops saw no serious problem to High Performance Java on sequential or Shared Memory Machines |
Some restrictions are needed in programming model
|
For instance, Avoid Complicated Exception handlers in areas compilers need to optimize! |
Should be able to get comparable performance on compiled Java C and Fortran starting with either Java Language or JavaVM bytecodes |
The Interpreted (Applet) JavaVM mode would always be slower than compiled Java/C/Fortran -- perhaps by a factor of two with best technology |
One can use "native classes" which is just a predownloaded library of optimized runtime routines which can be high performance compiled Java, C, C++, Fortran, HPF etc. modules invoked by interpreted or compiled Java
|
Use Native Classes selectively for
|
1)Classic solution of large scale PDE or Particle dynamics problem
|
2)Modest Grain size Functional Parallelism as seen in overlap of communication and computation in a node process of a parallel implementation.
|
3)Object parallelism seen in Distributed Simulation where "world" modelled (typically by event driven simulation) as set of interacting macroscopic (larger than grid points) objects
|
4)MetaProblems consisting of several large grain functionally distinct components such as
|
Java: 1) Not Supported, 2) is Thread mechanism, 3) is Java Objects or Applets, 4) is JavaBeans or equivalent |
Fortran: 1)is supported in HPF, 2--4) are not supported |
The Web integration of Java gives it excellent "network" classes and support for message passing. |
Thus "Java plus message passing" form of parallel computing is actually somewhat easier than in Fortran or C. |
Coarse grain parallelism very natural in Java |
"Data Parallel" languages features are NOT in Java and have to be added (as a translator) of HPJava to Java+Messaging just as HPF translates to Fortran plus message passing |
Java has built in "threads" and a given Java Program can run multiple threads at a time
|
Can be used to do more general parallel computing but only on shared memory computers
|
Combine threads on a shared memory machine with message passing between distinct distributed memories |
"Distributed" or "Virtual" Shared memory does support the JavaVM as hardware gives illusion of shared memory to JavaVM |
Message Passing |
Message Passing |
Java Wrappers (native classes or Server socket connections) around existing data parallel Fortran or C++ |
Native Java and MPI
|
Data Parallel Extensions of Java
|
Java threads for data parallelism on SMP's |