1 / 23

“Virtualisation and Parallelisation for using Opportunistic Idle CPU Resources”

“Virtualisation and Parallelisation for using Opportunistic Idle CPU Resources” MD. Mamunur Rashid (PhD Student ,LHCb). Optimistic......... Sure you need more hands . Task >Available Resources. Not Practical . Too practical . What can be consequence! . Consequence can be .

raoul
Download Presentation

“Virtualisation and Parallelisation for using Opportunistic Idle CPU Resources”

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. “Virtualisation and Parallelisation for using Opportunistic Idle CPU Resources” MD. Mamunur Rashid (PhD Student ,LHCb)

  2. Optimistic......... Sure you need more hands ...... Task >Available Resources

  3. Not Practical

  4. Too practical What can be consequence!

  5. Consequence can be ......

  6. We are missing something from all these pictures So what we missing ,is a harmony, a synchronization of using available resources

  7. We have these Parking Catalogue Parked on Friday Parked on 2/2/2008 Parked on Monday Parked 2/4/2009 Parked on Friday Parked on......... ..... Parked o........... Parked .............. Paarke............... Park................... Par....................... P........................ .......................... Parked ............n Proposal: Please don’t live your car here let some one use it you are not using.

  8. Why this approach is failed: Approach is not Practical : Car is very costly Potential Risk of Damage People have a habit of thinking it as very personal belongings So we had a prototype to solve a problem and it fails lets See if we can implement it any where else as its a promising approach

  9. Problem “We need to find more computational resources for accomplish our physics experiment” 1.On condition we don’t want to spend all our money to buy all the CPU. 2. What ever we buy today may be not enough for tomorrow. 3. So we need some thing for free or preferably cheap and unlimited

  10. we can’t use these machines , they are occupied Lets try some where else .......................

  11. What about these ones .. No occupied + Available + Idle

  12. What about these ones.................................................

  13. Or more interestingly these ones....... Occupied but not used ................ May be you gave up. but your machine is able to get some thing to do as they are not as lazy as we are. Lets called them Idle Machine

  14. Who are already using this idle resources SETI@home and some other projects using BOINC And they are : Active: 329,830 volunteers 574,820 computers. 24-hour average: 2,623.34 TeraFLOPS.

  15. Our contribution/Approach in this research field : “Virtualisation and Parallelisation for using opportunistic idle CPU resources”

  16. What we have for Parallelization : • We try to keep all the available cores busy to ensure full parallelization in instruction stream. • Implementation level will execute event/core: • Events size of 30-35 k • Recorded in 2 GB files • The first stage reconstruction • Takes 1-2s per event

  17. Basic Flow Form Storage To Storage Core Cloud Core Cloud (CC) Input Event Streem Input Event Streem Input Event Streem Input fileDB Output fileDB Input Event Streem Input Event Streem Input Event Streem Input Event Streem EvntA EvntB Evnt1 EvntB Input Event Streem EventCOllector Input Event Streem EvntG EvntR Evnt3 EvntA Evnt3 EvntX EvntR EvntF EvntK EvntV EvntD EvntG EvntN

  18. Basic structure of BOINC Interaction between client and server 2)Download application 3) Download Input files 4) Compute 5) Upload Output File 6) Report Result

  19. Technical/Scientific benefit of CernVM: 1. It will ensure the amount of exact acquired resources in the remote machine. (Soon Virtual machine is installed we know the system configuration(ram/harddrive size) and how much computation it can perform.) 2. It will facilitate access to use heterogeneous resources (MAC/LINUX/Windows..etc) 3. It will give a freedom to the volunteer user from installing every update of any available software by encapsulating operating system environment all in one (CernVM). 4. The virtual machine will come up with only strictly required software to minimise the overload of package size.( We can say it ThinVM)

  20. Where we want to be! Reconstruction Manager Input collector Worker node Output Collector Where all the available resource is being used and it would not effect us much if any of them is not performing as it will be a large collaborated resource sharing

  21. Where we can exercise this method 1.In Our online farm 2.Machine with multiple cores 3.Over Amazon/Google cloud @£/$/e(with CernVM) 4. Over the internet for opportunistic idle resource hunting using BOINC and CernVM

  22. Conclusion : So to run this project we have : DIRAC Single machine multiple core access mechanism CernVM BOINC (As an option) We can start with simulation So all we have to do integrate all these components together and monitor its performance and always try to find a better means to improve its performance . Is it all free!

  23. Many Thanks for Attending this Session : Question /Comments? My Comment :”lets Science Use it, when you don’t”

More Related