1 / 6

Possible uses of Everlab cluster Everlab Workshop 7-8 June, Jerusalem

Possible uses of Everlab cluster Everlab Workshop 7-8 June, Jerusalem. Iris Miliaraki Christos Tryfonopoulos . Dept . of Electronics and Computer Engineering Technical University of Crete. Technical University of Crete. Overview. Existing Systems Atlas LibraRing

kathie
Download Presentation

Possible uses of Everlab cluster Everlab Workshop 7-8 June, Jerusalem

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. Possible uses of Everlab clusterEverlab Workshop 7-8 June, Jerusalem Iris Miliaraki Christos Tryfonopoulos Dept. ofElectronics and Computer Engineering Technical University of Crete Technical University of Crete

  2. Overview • Existing Systems • Atlas • LibraRing • Current experiments • Future experiments

  3. The Atlas System • Atlas is a P2P system for the distributed storage and querying of RDF(S) data build on top of the Bamboo DHT (http://bamboo-dht.org). • Atlas is built in the context of the OntoGrid project. • Query-processing algorithms for the evaluation of queries on top of DHTs for RDF data. • Need to test performance by deploying Atlas in hundreds of nodes.

  4. The LibraRing System • Support full-fledged Information Retrieval and Filtering functionality in a P2P environment • A Chord variation is used as the routing infrastructure • Extra routing tables to reduce network traffic: • based on local interactions only • self-maintanable, self-tuning, correction-on-use • Need to test distributed resource and query indexing mechanisms in large-scale experiments

  5. Current experiments • Small-scale simulations only  • Using a Chord simulator • Metrics • network traffic created • load distribution • storage distribution • Need to test on a realistic setting

  6. Future experiments • Deploy Atlas and/or LibraRing on a cluster • Test different resource and query indexing algorithms • Test designed query-processing algorithms in a real implementation • By deploying a Chord-like system on a cluster

More Related