High performance Peer to Peer Distributed Computin

HighperformancePeertoPeerDistributedComputingwithApplicationtoObstacleProblemD.ELBAZ(LAAS-CNRS,ToulouseFrance)Coauthors:T.T.NGUYEN,P.SPITERI,G.JOURJON,M.CHAUfundedbyHOTP2P2010,April23,2010.HOTP2P2010,April23,2010.2OutlineEnvironment3Experiments45Conclusionstt1GoalSelf-adaptiveprotocol231.GoalGreatdevelopmentofpeertopeerapplicationsFilesharing,video,...Recentadvancesinmicroprocessorarchitectureandhighbandwithnetwork→newapplicationslikedistributedHPCcomputing/computingontheInternet.GreatchallengesScalability,Heterogeneity,Volatility,Existingprotocols,TCP,UDPnotwellsuitedtoHPC.HOTP2P2010,April23,2010.5234GoalProtocolEnvironmentExperiments15Conclusions41.Goal(cont’d)Highperformancepeertopeercomputing:Taskparallelmodel,distributediterativemethods.Directcommunicationsbetweenpeers.Applications:numericalsimulation&optimization.Self-adaptiveprotocol:basedonCactusframeworkusesmicro-protocolschoosesdynamicalythemostappropriatecommunica-tionmodeinfunctionofelementsofcontextfromnetworklevelandchoicesatapplicationlevel.HOTP2P2010,April23,2010.5234GoalProtocolEnvironmentExperiments15Conclusions52.Self-adaptiveprotocolMicro-protocolsIntroducedinx-kernelApproachtodesignself-adaptivecommunicationprotocolsMicro-protocolsimplementafunctionnality(sample)Communication:Synchronous,Asynchronous.Fragmentation:FixeSize,Resize.Reliability:Retransmission,PositiveAck,NegativeAck,DuplicateAck.Order:LossyFifo,ReliableFifo.Congestioncontrol:NewRenoTCPCongestionControl.Compositionofmicro-protocols→protocolReusecode,facilitatedesign,configuredynamically.HOTP2P2010,April23,2010.Protocol54GoalEnvironmentExperiments1532Conclusions62.Self-adaptiveprotocol(cont’d)Protocolcompositionframework→deploymentofarchitectureHierarchicalmodel(stackofprotocols),x-kernel,APPIAframeworks.Nonhierarchicalmodel(noorder),CoyoteandADAPTIVEframe’ks.Hybridmodel(combo),XQoSandCactusframeworks→CTP.Cactusframeworkflexible,efficient.Twograinlevels:Compositeprotocols:individualprotocolmadeofmicro-protocols.Protocolstack:compositeprotocolslayeredonthetopofeachothers.Protocolscanreconfigurebysubstitutingprotocolsormicro-protocols.HOTP2P2010,April23,2010.Protocol54GoalEnvironmentExperiments1532Conclusions72.Self-adaptiveprotocol(cont’d)Cactusisaneventbasedframework:Events:statechanges,e.g.arrivalofmessages.Micro-protocolsstructuredasacollectionofeventhandlers:Eventhandler:procedurelikesegmentsofcodesboundtoevents.Whenaneventoccursallhandlersboundtothateventareexecuted.OurmodificationstoCactus→improveprotocolperformance/facilitatereconfiguration:Concurrenthandlerexecution(multicoremachines).Eliminateunnecessarycopiesbetweenlayers(usepointers)Operationformicro-protocolremoving.HOTP2P2010,April23,2010.Protocol54GoalEnvironmentExperiments1532Conclusions82.Self-adaptiveprotocol(cont’d)P2PSAPprotocolarchitectureHOTP2P2010,April23,2010.Protocol54GoalEnvironmentExperiments1532Conclusions~~~~~~~~~~~PhysicallayerTransportlayerAPI~~~~~~~~~~~ManagessessionopeninganclosureCapturescontextinformationReconfiguresdatachannel/coordinatespeersTransfersdatabetweenpeers92.Self-adaptiveprotocol(cont’d)CommunicationadaptationrulesHOTP2P2010,April23,2010.SchemeLinkSynchronousAsynchronousHybridIntra-clusterSynchronousReliableCom.AsynchronousReliableCom.SynchronousReliableCom.Inter-clusterSynchronousReliableCom.AsynchronousUnreliableCom.AsynchronousUnreliableCom.Protocol54GoalEnvironmentExperiments1532Conclusions102.Self-adaptiveprotocol(cont’d)ReconfigurationmechanismHOTP2P2010,April23,2010.Protocol54GoalEnvironmentExperiments1532Conclusions112.Self-adaptiveprotocol(cont’d)ExampleofscenarioHOTP2P2010,April23,2010.Protocol54GoalEnvironmentExperiments1532Conclusions123.EnvironmentDirectcommunicationbetweenpeersReducedsetofcommunicationoperations:-onlysendandreceiveoperations(P2P_sendandP2P_receive).-facilitateprogramming,hidecomplexity.Communicationmodecanvarywithcontext:-programmerdoesnotselectdirectlyacommunicationmode(programmercanselectaschemeofcomputation).-communicationmodedependsonthecontextandisdeterminedbytheprotocol.-goodefficiency.HOTP2P2010,April23,2010.Protocol54GoalEnvironmentExperiments1532Conclusions133.Environment(cont’d)P2PDCEnvironmentarchitectureHOTP2P2010,April23,2010.Protocol54GoalEnvironmentExperiments1532Conclusions143.Environment(cont’d)ApplicationdeploymentHOTP2P2010,April23,2010.Protocol54GoalEnvironmentExperiments1532Conclusions154.Experiments3DObstacleproblem-numericalsimulationproblems(pde)-financialmathematics,e.g.optionpricing-mechanicsHOTP2P2010,April23,2010.ProtocolGoalEnvironmentExperiments515324Conclusions164.Experiments(cont’d)Fixedpointproblem:Distributedasynchronousiterativescheme:HOTP2P2010,April23,2010.ProtocolGoalEnvironmentExperiments515324Conclusions(5)174.Experiments(cont’d)Results3Dobstacleproblem,slicedecomposition,3,000,000variables,NICTAtestbed,Sidney.HOTP2P2010,April23,2010.ProtocolGoalEnvironmentExperiments515324Conclusions185.ConclusionsSelf-adaptiveprotocolP2PSAPforP2PHPCCurrentversionofenv