SlideShare uma empresa Scribd logo
1 de 5
Baixar para ler offline
System Installation and Configuration

Introduction
SixFaceCloud is a platform for solving financial analytics and quantitative analysis tasks using distributed
computing. The solution consists of two main parts: Execution Engine and development tools. Facilitate
application development using advanced tools; run your financial calculations on a local PC, local area
network or in a cloud environment without source code change.

Quant can develop financial model using SixFaceCloud framework (Java or DSL) and execute it in
required Execution Engine context: locally, in local network cluster, on Amazon EC2 and on GPU
(coming soon).

The user just needs to change few lines in a configuration file to offload the execution of a function to
local network or cloud based servers. SixFaceCloud will deploy all the code to the execution
environment and run it for you. Getting on the cloud has never been this easy!

SixFaceCloud improves the full cycle of software development and deployment. No additional
deployment steps are required in order to run your software on a cloud environment.
SixFaceCloud enables you to develop faster, easier, and smarter.

System Structure
SixFaceCloud consists of 2 parts:

•   Development tools: Java framework and SFC Domain Specific Language(DSL).
    Tools are designed for rapid development of quantitative models (based on Monte Carlo methods
    for example) and for communicating with Execution Engine.
•   Execution Engine which can be installed in the local network or in a data center.
    It is designed for distributed execution of financial models created within SixFaceCloud Java frame-
    work or SixFaceCloud DSL. Download Execution Engine.

Below is a short instruction on how to configure Execution Engine for local cluster
SixFaceCloud infrastructure contains a single cloud server and multiple cloud workers. Adding more
worker nodes to the system increases computing power improving performance of Monte Carlo
simulations. SixFaceCloud provides server and workers service libraries: cloud_server and cloud_worker.




                                      © Copyright 2012 SixFaceCloud, Inc.                                      1
Cloud




                                               Communication data  :
                                               - Server static IP
                                               - Client connection port
                                               - Workers connection port




               Cloud client                      Cloud server




                                                                             Cloud workers

Network requirement: server must have static IP address!

Note that cloud server and cloud workers should be in the same network and client computer should
be able to establish TCP connection with cloud server (i.e.: client computer can be in another network).

System Configuration
Server’s IP address must be defined in configuration files of the cloud server and workers

   config/cloud_server/spring_cloud_server.xml property cloud.address
   config/cloud_worker/spring_cloud_worker.xml property cloud.address

Below is a code snippet from configuration file that needs to be modified.

Substitute YOUR_SERVER_HOST with your real server host address.

        <!--
        Change YOUR_SERVER_HOST value to your real server host address.
        Note please, that it should not be '127.0.0.1' or 'localhost' values.
        -->
        <bean id="cloud.address" class="java.lang.String" lazy-init="false">
             <constructor-arg value="YOUR_SERVER_HOST:47500" />
        </bean>

Make sure that ports 5678, 5679, and 47500 are open and free on the server node. Please check
according policy if you are using Amazon EC2 hosting. If you can't use these ports, change serverPort
and workerCommunicationPort in config/cloud_server/spring_cloud_server.xml file (see property
‘comm.srv’).




                                     © Copyright 2012 SixFaceCloud, Inc.                                   2
System Installation
Just copy the content of delivery folder to a server and workers.

Starting the System
 Run the server with server.cmd/sh (start server)
 Run every worker with worker.cmd/sh (start workers)

Server must be started prior to workers. It is not necessary to restart already running workers if a server
is turned off. However, new workers will not be able to start without a running server instance.

Additional configuration parameters

Additional server settings:
File: config/cloud_server/spring_cloud_server.xml, service: ‘comm.srv’:

        Parameter                  Default value                              Description

cloudClientPort                5678                   Cloud server connection port. It uses to connect to the
                                                      cloud from the client side.

workerCommunicationPort        5679                   Cloud server connection port. The same value should be
                                                      set on server and worker sides.

classRequestTimeout            5000 ms                Distributed class-loader timeout.

randomServiceTimeout           2000 ms                Random services communication timeout between
                                                      server and workers.

debugStatistic                 False                  Turn on/off statistic service debug mode.

calcOnCoordinatorSide          False                  Identifies if a server node takes part in calculation.

corePoolSize                   1                      Parameter of the cloud server thread pool executor that
                                                      is designed to communicate between cloud server, and
                                                      workers, cloud clients.

execAttempts                   3                      Number of execution attempts if user task is rejected
                                                      from cloud server thread pool executor.

execErrorWaitTime              500 ms                 Time in milliseconds before next execution attempt if
                                                      user task is rejected from cloud server thread pool
                                                      executor.

heartbeatTime                  3000 ms                Heartbeat interval between cloud sever and cloud
                                                      client.

keepAliveTime                  0                      Parameter of cloud server thread pool executor that is
                                                      designed to communicate between cloud server and
                                                      workers, cloud clients.

maxBatchOnNode                 50                     Maximum number of batches on one node. If user
                                                      defined value is greater than given value, batch size
                                                      should be increased, but batch quantity - decreased.


                                       © Copyright 2012 SixFaceCloud, Inc.                                      3
maximumPoolSize                200                   Parameter of cloud server thread pool executor that is
                                                     designed to communicate between cloud server and
                                                     workers, cloud clients.

maxMemoryUsage                 67108864 bytes        Maximum size in bytes of an object’s summary that can
                                                     be accumulated in user code.

maxObjects                     100000                Maximum number of objects that can be accumulating
                                                     in user code.

maxTaskTime                    60000 ms              Maximum task execution time. User defined task
                                                     execution time can be smaller, but not greater than this
                                                     value.

missedHeartbeatCount           3                     Maximum number of missed heartbeats between cloud
                                                     server and cloud client. The connection will be forced
                                                     to close after this number is reached.

serverSocketReconnectTime 500 ms                     Sleep time between server sockets creation after IO
                                                     errors.

disconnectTime                 500 ms                Sleep time before closing client connection.

disconnectTime                 500 ms                Sleep time before closing cloud client connection.



File: config/cloud_server/spring_cloud_server.xml, service: ‘stat.srv’

         Parameter                 Default value                             Description

turnedOn                       True                  Turn on/off statistic service.




                                      © Copyright 2012 SixFaceCloud, Inc.                                       4
Additional workers settings:
File: config/cloud_worker/spring_cloud_worker.xml, service: ’comm.srv’

         Parameter              Default value                                Description

workerCommunicationPort       5679                   Communication connection port between server and
                                                     workers. The same value should be set on server and
                                                     workers side.

classRequestTimeout           5000 ms                Distributed class-loader timeout.

randomServiceTimeout          2000 ms                Random services communication timeout between
                                                     server and workers.

debugStatistic                False                  Turn on/off statistic service debug mode.

calcOnCoordinatorSide         False                  Identifies if a server node takes part in calculation.




                                      © Copyright 2012 SixFaceCloud, Inc.                                     5

Mais conteúdo relacionado

Destaque (9)

Curs mobile marketing
Curs mobile marketingCurs mobile marketing
Curs mobile marketing
 
Rio para coloriqr
Rio para coloriqrRio para coloriqr
Rio para coloriqr
 
Aziende confiscate, boom di fallimenti
Aziende confiscate, boom di fallimentiAziende confiscate, boom di fallimenti
Aziende confiscate, boom di fallimenti
 
Jp morgan singapore sustainable cities
Jp morgan singapore sustainable citiesJp morgan singapore sustainable cities
Jp morgan singapore sustainable cities
 
How to inform your clients
How to inform your clients How to inform your clients
How to inform your clients
 
[Jpeg](adab)lesson#3 covenant
[Jpeg](adab)lesson#3   covenant[Jpeg](adab)lesson#3   covenant
[Jpeg](adab)lesson#3 covenant
 
Rio para colorxir
Rio para colorxirRio para colorxir
Rio para colorxir
 
Trabajo tarde 2
Trabajo tarde 2Trabajo tarde 2
Trabajo tarde 2
 
X 47 B Experimental Aircraft
X 47 B Experimental AircraftX 47 B Experimental Aircraft
X 47 B Experimental Aircraft
 

Último

Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Victor Rentea
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Safe Software
 
Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
WSO2
 

Último (20)

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood
Polkadot JAM Slides - Token2049 - By Dr. Gavin WoodPolkadot JAM Slides - Token2049 - By Dr. Gavin Wood
Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood
 
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWEREMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
 
ICT role in 21st century education and its challenges
ICT role in 21st century education and its challengesICT role in 21st century education and its challenges
ICT role in 21st century education and its challenges
 
CNIC Information System with Pakdata Cf In Pakistan
CNIC Information System with Pakdata Cf In PakistanCNIC Information System with Pakdata Cf In Pakistan
CNIC Information System with Pakdata Cf In Pakistan
 
WSO2's API Vision: Unifying Control, Empowering Developers
WSO2's API Vision: Unifying Control, Empowering DevelopersWSO2's API Vision: Unifying Control, Empowering Developers
WSO2's API Vision: Unifying Control, Empowering Developers
 
Corporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptxCorporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptx
 
DBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor PresentationDBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor Presentation
 
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemkeProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
 
Strategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a FresherStrategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a Fresher
 
Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024
 
Exploring Multimodal Embeddings with Milvus
Exploring Multimodal Embeddings with MilvusExploring Multimodal Embeddings with Milvus
Exploring Multimodal Embeddings with Milvus
 
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, AdobeApidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
 
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...
"I see eyes in my soup": How Delivery Hero implemented the safety system for ..."I see eyes in my soup": How Delivery Hero implemented the safety system for ...
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
 
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost SavingRepurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
 
Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
 
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
 
Six Myths about Ontologies: The Basics of Formal Ontology
Six Myths about Ontologies: The Basics of Formal OntologySix Myths about Ontologies: The Basics of Formal Ontology
Six Myths about Ontologies: The Basics of Formal Ontology
 
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdfRising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
 
presentation ICT roal in 21st century education
presentation ICT roal in 21st century educationpresentation ICT roal in 21st century education
presentation ICT roal in 21st century education
 

SixFaceCloud Installation

  • 1. System Installation and Configuration Introduction SixFaceCloud is a platform for solving financial analytics and quantitative analysis tasks using distributed computing. The solution consists of two main parts: Execution Engine and development tools. Facilitate application development using advanced tools; run your financial calculations on a local PC, local area network or in a cloud environment without source code change. Quant can develop financial model using SixFaceCloud framework (Java or DSL) and execute it in required Execution Engine context: locally, in local network cluster, on Amazon EC2 and on GPU (coming soon). The user just needs to change few lines in a configuration file to offload the execution of a function to local network or cloud based servers. SixFaceCloud will deploy all the code to the execution environment and run it for you. Getting on the cloud has never been this easy! SixFaceCloud improves the full cycle of software development and deployment. No additional deployment steps are required in order to run your software on a cloud environment. SixFaceCloud enables you to develop faster, easier, and smarter. System Structure SixFaceCloud consists of 2 parts: • Development tools: Java framework and SFC Domain Specific Language(DSL). Tools are designed for rapid development of quantitative models (based on Monte Carlo methods for example) and for communicating with Execution Engine. • Execution Engine which can be installed in the local network or in a data center. It is designed for distributed execution of financial models created within SixFaceCloud Java frame- work or SixFaceCloud DSL. Download Execution Engine. Below is a short instruction on how to configure Execution Engine for local cluster SixFaceCloud infrastructure contains a single cloud server and multiple cloud workers. Adding more worker nodes to the system increases computing power improving performance of Monte Carlo simulations. SixFaceCloud provides server and workers service libraries: cloud_server and cloud_worker. © Copyright 2012 SixFaceCloud, Inc. 1
  • 2. Cloud Communication data : - Server static IP - Client connection port - Workers connection port Cloud client Cloud server Cloud workers Network requirement: server must have static IP address! Note that cloud server and cloud workers should be in the same network and client computer should be able to establish TCP connection with cloud server (i.e.: client computer can be in another network). System Configuration Server’s IP address must be defined in configuration files of the cloud server and workers  config/cloud_server/spring_cloud_server.xml property cloud.address  config/cloud_worker/spring_cloud_worker.xml property cloud.address Below is a code snippet from configuration file that needs to be modified. Substitute YOUR_SERVER_HOST with your real server host address. <!-- Change YOUR_SERVER_HOST value to your real server host address. Note please, that it should not be '127.0.0.1' or 'localhost' values. --> <bean id="cloud.address" class="java.lang.String" lazy-init="false"> <constructor-arg value="YOUR_SERVER_HOST:47500" /> </bean> Make sure that ports 5678, 5679, and 47500 are open and free on the server node. Please check according policy if you are using Amazon EC2 hosting. If you can't use these ports, change serverPort and workerCommunicationPort in config/cloud_server/spring_cloud_server.xml file (see property ‘comm.srv’). © Copyright 2012 SixFaceCloud, Inc. 2
  • 3. System Installation Just copy the content of delivery folder to a server and workers. Starting the System  Run the server with server.cmd/sh (start server)  Run every worker with worker.cmd/sh (start workers) Server must be started prior to workers. It is not necessary to restart already running workers if a server is turned off. However, new workers will not be able to start without a running server instance. Additional configuration parameters Additional server settings: File: config/cloud_server/spring_cloud_server.xml, service: ‘comm.srv’: Parameter Default value Description cloudClientPort 5678 Cloud server connection port. It uses to connect to the cloud from the client side. workerCommunicationPort 5679 Cloud server connection port. The same value should be set on server and worker sides. classRequestTimeout 5000 ms Distributed class-loader timeout. randomServiceTimeout 2000 ms Random services communication timeout between server and workers. debugStatistic False Turn on/off statistic service debug mode. calcOnCoordinatorSide False Identifies if a server node takes part in calculation. corePoolSize 1 Parameter of the cloud server thread pool executor that is designed to communicate between cloud server, and workers, cloud clients. execAttempts 3 Number of execution attempts if user task is rejected from cloud server thread pool executor. execErrorWaitTime 500 ms Time in milliseconds before next execution attempt if user task is rejected from cloud server thread pool executor. heartbeatTime 3000 ms Heartbeat interval between cloud sever and cloud client. keepAliveTime 0 Parameter of cloud server thread pool executor that is designed to communicate between cloud server and workers, cloud clients. maxBatchOnNode 50 Maximum number of batches on one node. If user defined value is greater than given value, batch size should be increased, but batch quantity - decreased. © Copyright 2012 SixFaceCloud, Inc. 3
  • 4. maximumPoolSize 200 Parameter of cloud server thread pool executor that is designed to communicate between cloud server and workers, cloud clients. maxMemoryUsage 67108864 bytes Maximum size in bytes of an object’s summary that can be accumulated in user code. maxObjects 100000 Maximum number of objects that can be accumulating in user code. maxTaskTime 60000 ms Maximum task execution time. User defined task execution time can be smaller, but not greater than this value. missedHeartbeatCount 3 Maximum number of missed heartbeats between cloud server and cloud client. The connection will be forced to close after this number is reached. serverSocketReconnectTime 500 ms Sleep time between server sockets creation after IO errors. disconnectTime 500 ms Sleep time before closing client connection. disconnectTime 500 ms Sleep time before closing cloud client connection. File: config/cloud_server/spring_cloud_server.xml, service: ‘stat.srv’ Parameter Default value Description turnedOn True Turn on/off statistic service. © Copyright 2012 SixFaceCloud, Inc. 4
  • 5. Additional workers settings: File: config/cloud_worker/spring_cloud_worker.xml, service: ’comm.srv’ Parameter Default value Description workerCommunicationPort 5679 Communication connection port between server and workers. The same value should be set on server and workers side. classRequestTimeout 5000 ms Distributed class-loader timeout. randomServiceTimeout 2000 ms Random services communication timeout between server and workers. debugStatistic False Turn on/off statistic service debug mode. calcOnCoordinatorSide False Identifies if a server node takes part in calculation. © Copyright 2012 SixFaceCloud, Inc. 5