Dear IBR-DTN Community,
Currently I'm looking into the bundle queuing of IBR-DTN. In the code of IBR-DTN_1.0.1 I've found different queue implementations for HDD (SimpleBundleStorage) and memory (MemoryBundleStorage). i.e. In the SimpleBundleStorage _priority_index queue is encapsulated by the class MetaStorage and in the MemoryBundleStorage it is not. Is there a specific reason for the difference in the context of memory management?
Best Regards, Alex van der Linden
Hello Alex,
there is no 'specific' reason for that. It is more a historical engineering decision. The memory-based storage was the first which got implemented. In the later development, the disk-based variant was implemented to support devices with small amounts of memory. To achieve a high performance, the disk operations are processed within a separate thread. In the memory-based implementation this is not necessary, because there are no long blocking operations.
Kind regards, Johannes
Am 20.04.2015 um 10:24 schrieb Alex van der Linden:
Currently I'm looking into the bundle queuing of IBR-DTN. In the code of IBR-DTN_1.0.1 I've found different queue implementations for HDD (SimpleBundleStorage) and memory (MemoryBundleStorage). i.e. In the SimpleBundleStorage _priority_index queue is encapsulated by the class MetaStorage and in the MemoryBundleStorage it is not. Is there a specific reason for the difference in the context of memory management?
participants (2)
-
Alex van der Linden
-
Johannes Morgenroth