Bitcoin Forum
December 10, 2016, 07:05:16 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: bitcoind 17mb? How to shrink it after compiling?  (Read 1061 times)
payb.tc
Hero Member
*****
Offline Offline

Activity: 812



View Profile
July 31, 2011, 08:00:02 AM
 #1

after compiling bitcoind it's come out as 17mb... it actually runs fine (finally, yay!), but I'm wondering what is the final step in the process... what util would one use to strip it down to the size that normally gets released?
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481353516
Hero Member
*
Offline Offline

Posts: 1481353516

View Profile Personal Message (Offline)

Ignore
1481353516
Reply with quote  #2

1481353516
Report to moderator
1481353516
Hero Member
*
Offline Offline

Posts: 1481353516

View Profile Personal Message (Offline)

Ignore
1481353516
Reply with quote  #2

1481353516
Report to moderator
Sukrim
Legendary
*
Offline Offline

Activity: 1848


View Profile
July 31, 2011, 08:11:27 AM
 #2

Maybe you compiled it with debug code?

https://bitfinex.com <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with this refcode: x5K9YtL3Zb
Mail me at Bitmessage: BM-BbiHiVv5qh858ULsyRDtpRrG9WjXN3xf
mrb
Legendary
*
Offline Offline

Activity: 1120


View Profile WWW
July 31, 2011, 09:36:20 AM
 #3

what util would one use to strip it down to the size that normally gets released?

Simply "strip bitcoin"!
payb.tc
Hero Member
*****
Offline Offline

Activity: 812



View Profile
July 31, 2011, 09:49:45 AM
 #4

thank you! duh.
JoelKatz
Legendary
*
Offline Offline

Activity: 1386


Democracy is vulnerable to a 51% attack.


View Profile WWW
August 01, 2011, 05:44:46 AM
 #5

I would recommend not stripping it unless you have some specific need to. The larger size is due to debug information that is never loaded or used when the program is running (it doesn't actually bloat memory or slow execution in any way). But without it, you cannot make sense of core dumps.

I am an employee of Ripple.
1Joe1Katzci1rFcsr9HH7SLuHVnDy2aihZ BM-NBM3FRExVJSJJamV9ccgyWvQfratUHgN
ShadowOfHarbringer
Legendary
*
Offline Offline

Activity: 1470


Bringing Legendary Har® to you since 1952


View Profile
September 22, 2011, 10:10:58 AM
 #6

I would recommend not stripping it unless you have some specific need to. The larger size is due to debug information that is never loaded or used when the program is running (it doesn't actually bloat memory or slow execution in any way). But without it, you cannot make sense of core dumps.

I have just compiled it and it is also 17 MB...

So you are saying this is completely normal, and i have absolutely nothing to worry about, including running that version on production servers ?

ShadowOfHarbringer
Legendary
*
Offline Offline

Activity: 1470


Bringing Legendary Har® to you since 1952


View Profile
September 22, 2011, 11:12:22 AM
 #7

Update:

It would appear that the unstripped version is not production safe. It damaged the database and now when i try to run normal (non-compiled) client, it crashes with following error:

Quote
************************
EXCEPTION: 22DbRunRecoveryException      
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery      
bitcoin in AppInit()      

terminate called after throwing an instance of 'DbRunRecoveryException'
  what():  DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery

EDIT:
Actually, I can only run compiled versions now, the binary version from bitcoin.org crashes every time i try to launch it using the same database. Any ideas ?

Perhaps different version of BerkeleyDB on my debian system or whatever ?

ArtForz
Sr. Member
****
Offline Offline

Activity: 406


View Profile
September 22, 2011, 12:25:38 PM
 #8

the database format itself is compatible, the transaction logs are not. remove /database/log.* while bitcoind is stopped and you can happily switch from bdb5.1 back to 4.6 and similar stunts.

bitcoin: 1Fb77Xq5ePFER8GtKRn2KDbDTVpJKfKmpz
i0coin: jNdvyvd6v6gV3kVJLD7HsB5ZwHyHwAkfdw
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!