Peter Surda
0c9cb4824d
- objectsKnownToThem is supposed to track if it's necessary to send inv commands to a peer - it is supposed to enter garbage collection after 1 hour (ObjectTracker.trackingExpires) - due to peer not announcing all objects, or announcing them before we announce, this contains excessive number of entries after connection is fully established. - profiling revealed that this creates unnecessary memory to be kept allocated - this patch will prevent tracking of entries sent during bigInv, reducing the memory "leak" - it is possible, in theory, that this does have some negative effect, like increased bandwidth or neglecting to announce some invs. It probably doesn't though as my review of objectsKnownToThem occurrences didn't reveal any such case, and since the dict didn't track fully accurately anyway (so it would have already been broken if it was a problem), I consider it an acceptable risk at the moment. If it indeed causes problems, they can be solved separately - I tested this on one of the bootstrap servers with little memory, and it increased the number of connections than can be handled by a factor of about 3.5 |
||
---|---|---|
build | ||
desktop | ||
dev | ||
man | ||
packages | ||
src | ||
.gitignore | ||
checkdeps.py | ||
configure | ||
COPYING | ||
INSTALL.md | ||
LICENSE | ||
MANIFEST.in | ||
PULL_REQUEST_TEMPLATE.md | ||
README.md | ||
setup.py |
PyBitmessage
Bitmessage is a P2P communication protocol used to send encrypted messages to another person or to many subscribers. It is decentralized and trustless, meaning that you need-not inherently trust any entities like root certificate authorities. It uses strong authentication, which means that the sender of a message cannot be spoofed. BM aims to hide metadata from passive eavesdroppers like those ongoing warrantless wiretapping programs. Hence the sender and receiver of Bitmessages stay anonymous.
Development
Bitmessage is a collaborative project. You are welcome to submit pull requests although if you plan to put a non-trivial amount of work into coding new features, it is recommended that you first solicit feedback on the DevTalk pseudo-mailing list: BM-2D9QKN4teYRvoq2fyzpiftPh9WP9qggtzh
Feel welcome to join chan "bitmessage", BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY which is on preview here: http://beamstat.com/chan/bitmessage