Opened at 2008-05-15T12:46:27Z
Last modified at 2011-01-02T14:53:19Z
#4 new enhancement
pycryptopp uses up too much memory at runtime
Reported by: | zooko | Owned by: | warner |
---|---|---|---|
Priority: | minor | Milestone: | |
Version: | 0.5.1 | Keywords: | |
Cc: | Launchpad Bug: |
Description
http://allmydata.org/trac/tahoe/ticket/419 (pycryptopp uses up too much space)
Change History (4)
comment:1 Changed at 2008-05-15T12:53:10Z by zooko
- Status changed from new to accepted
- Version set to 0.5.1
comment:2 Changed at 2008-06-19T22:41:37Z by warner
- Summary changed from pycryptopp uses up too much space to pycryptopp uses up too much memory at runtime
comment:3 Changed at 2011-01-02T14:53:12Z by zooko
- Status changed from accepted to new
Brian: it is now possible to link to an external libcryptop++.so (build with --disable-embedded-cryptopp option to setup.py). How could we determine whether this ticket should be closed -- let you eyeball the results of "top" while running Tahoe-LAFS with a modern pycryptopp? (Or maybe eyeball the results of smem?)
comment:4 Changed at 2011-01-02T14:53:19Z by zooko
- Owner changed from zooko to warner
Note: See
TracTickets for help on using
tickets.
note that dynamically linking against a single external libcrypto++.so is likely to help: see #9