OverSim vs. Overlay Weaver

Quick comparison on OverSim & Overlay Weaver

OverSim	Overlay Weaver
Simulator	Emulator
OMNet++ based	Stand alone package
C++ based. Some parts of the code is expected to be use for production	Java based. Code is expected to be use for production
GUI for demonstrations - more features	GUI for demonstrations
No documentation - High learning curve	No documentation - High learning curve
Statistics, visualizing tools, vectors (time series)	Some statistics
Many built in overlays - Chord, Pastry, Bamboo, Koorde, Broose, Kademlia, GIA, NICE, NTree, Quon, Vast, & Publish-Subscribe	Built in overlays - Chord, Kademlia, Koorde, Pastry, Tapestry & FRT-Chord
Built in routing modes - Recursive, iterative, semi-recursiv, exhaustive-iterativee	Built in routing modes - Recursive, iterative
Built in applications - DHT, i3, scribe, P2PNS, KBRTestApp, DHTTestApp, & SimpleGameClient	DHT & multicast
Relatively Fast - Up to 100,000 nodes	Several thousand.
Underlay - simple & INETUnderlay. UDP & TCP on IPv4/IPV6	Suppose to be work on a real network
Churn - Lifetime & Pareto	No information
GNU GPL	Apache License
No demos	Online demonstration of a DHT using PlanetLab. Some videos

Comments

1. Building P2P Simulators with OverSim - Where to Begin

This could be a series of blog posts about extending or developing your own OverSim applications & overlay networks. OverSim has a minimal tutorial on writing your own application & overlay network; however, it doesn't show the big picture. So, I'm wasting lots of time playing with code & trying to understand the rest. Good thing is, I like it more & more as I understand. You need to change/develop only a few things, but finding out which ones is a hell of a task. I hope this will not only make my life easy but also will be useful to new comers. Here's what you need to do: You need some background on OMNeT++ OverSim extend OMNeT++. But sometime it has its own way of doing things (to make your task even simple) so understand the differences . Develop several OMNeT++ simulators. TicToc is a good one to start with. Extend it as you imagine. Read Towards a Common API for Structured Peer-to-Peer Overlays , which is the basis for OvseSim's AP

Describing Experimental/Simulation Setup

Sometimes the results of a performance analysis may depend on the computers used and/or specific features of software/libraries. In such cases it is extremely important to describe the experimental/simulation set up in details. It enables others to repeat those experiments as well as check whether the results are rigorous, statistically sound, and unbiased. Unfortunately, "Simulation Setup" is the shortest section in many research papers where authors try to save space by cutting down as much as details. Here are some tips on what to include (in addition to describing the experimental/simulation setup) based on my experiences: Type of Simulation Are the results based on Experimentation , Emulation , or Simulation ? If simulations also mention further details like whether it is Discrete Event , Montacarlo , Stochastic , or Deterministic simulation. Are the results for Steady , Dynamic , Starting/ramp-up , or Terminating state(s)? Number of Exp

Distributed Systems Mind Map

Though distributed systems are inherently distributed, autonomous, and parallel, all textbooks that I have read so far are boring & serial, going from one topic to another as they are independent topics. Wondering about how best to present all related topics and their relationships in my class, I came up with the following mind map. I was able to explain most of the key concepts using a single example of a web-based business that started selling flowers. It was a student who suggested that we consider selling flowers. It turned out to be a good example, as there had to be a connection to the physical world where the business also needed a geographical distributed delivery system. Taught of sharing the mind map. Though most of those branches can be broken down further this level of detailed was sufficient for my class (by the way it took 1 hour to finish the discussion on this slide). Distributed Systems Mind Map

Dilum Bandara

Search This Blog