Skip to main content

OverSim vs. Overlay Weaver

Quick comparison on OverSim & Overlay Weaver
OverSimOverlay Weaver
SimulatorEmulator
OMNet++ basedStand alone package
C++ based. Some parts of the code is expected to be use for productionJava based. Code is expected to be use for production
GUI for demonstrations - more featuresGUI for demonstrations
No documentation - High learning curveNo 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-SubscribeBuilt in overlays - Chord, Kademlia, Koorde, Pastry, Tapestry & FRT-Chord
Built in routing modes - Recursive, iterative, semi-recursiv, exhaustive-iterativeeBuilt in routing modes - Recursive, iterative
Built in applications - DHT, i3, scribe, P2PNS, KBRTestApp, DHTTestApp, & SimpleGameClientDHT & multicast
Relatively Fast - Up to 100,000 nodesSeveral thousand.
Underlay - simple & INETUnderlay. UDP & TCP on IPv4/IPV6Suppose to be work on a real network
Churn - Lifetime & ParetoNo information
GNU GPLApache License
No demosOnline demonstration of a DHT using PlanetLab. Some videos

Comments

Popular posts from this blog

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...

Key Application Layer Functions

Constructor  Can be use to set message to NULL . Better not to skip defining the constructor. Destructor Can be use to clear/delete messages using cancelAndDelete() . New version seems to be motivating to use a destructor so better not to skip. void initializeApp(int stage) Can be used to initialize the application, read parameters from omnet.ini file, set statistic collectors, GUI display variables, start timers, set UDP port, etc. stage - Indicate which stage your are in. MIN_STAGE_APP indicates this module is being created while MAX_STAGE_APP indicates all modules were created. We typically need MIN_STAGE_APP to i nitialize application & variables. void finishApp() Called when application is terminating. Can be used to summarize stat. New version seems to be motivating us to delete messages in the destructor.   void handleTimerEvent(cMessage* msg) Handle event timer. Use to generate new periodic messages, other events, or check for lost messages. Bett...

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