[XMR] Monero - A secure, private, untraceable cryptocurrency

[Cablez]

So I have fully synchronized with the monero blockchain on 0.9 beta windows.  These are inconsistencies I have noticed:

1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.

2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.

3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.

The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.

Has anyone else running the beta code noticed issues similarly?

[1715394771]

1715394771

[1715394771]

1715394771

[1715394771]

1715394771

[1715394771]

1715394771

[1715394771]

1715394771

[vvrroomm]

Monero Specifications

•PoW algorithm: CryptoNight [1]
•Max supply: Infinite (see note below) [2]
•Block reward: Smoothly varying [3]

Finally fixed the max supply.  Nice stealth update! So now the coin has infinite amounts!  LOL

TO INFINITY AND BEYOND LOL!

[saddambitcoin]

So I have fully synchronized with the monero blockchain on 0.9 beta windows.  These are inconsistencies I have noticed:

1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.

2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.

3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.

The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.

Has anyone else running the beta code noticed issues similarly?

I'm not running the windows beta, but in response to #2, that sounds about right: the blockchain is ~14 Gb on my computer.

[dEBRUYNE]

So I have fully synchronized with the monero blockchain on 0.9 beta windows.  These are inconsistencies I have noticed:

1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.

2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.

3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.

The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.

Has anyone else running the beta code noticed issues similarly?

[1] Are you sure it isn't still syncing? Check the blockheight at the daemon and compare that with the blockheight on https://moneroblocks.eu. I think the green line in bitmonerod (stating something like, you are now fully synced and are able to use simplewallet) already appears somewhat before you are fully synced. LMDB only takes what it can take (during syncing). If much of your RAM is already allocated, LMDB won't take it while syncing. In other words, it won't get stuck like for instance the old binaries. After syncing it only takes <100 MB.

[2] That seems to be correct, the RAW file is around 2.3 GB. The size reported by you is the database representation used by the daemon. In my opinion, 14 GB isn't that much if you have a decent PC with a decent HDD/SSD. Currently, most of them have plenty of GBs and 14 GB is relatively small compared to that.

[3] If you mean the third party GUIs, that is correct. I think the developers of them will merge LMDB when it is officially released.

[luigi1111]

So I have fully synchronized with the monero blockchain on 0.9 beta windows.  These are inconsistencies I have noticed:

1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.

2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.

3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.

The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.

Has anyone else running the beta code noticed issues similarly?

[1] Are you sure it isn't still syncing? Check the blockheight at the daemon and compare that with the blockheight on https://moneroblocks.eu. I think the green line in bitmonerod (stating something like, you are now fully synced and are able to use simplewallet) already appears somewhat before you are fully synced. LMDB only takes what it can take (during syncing). If much of your RAM is already allocated, LMDB won't take it while syncing. In other words, it won't get stuck like for instance the old binaries. After syncing it only takes <100 MB.

[2] That seems to be correct, the RAW file is around 2.3 GB. The size reported by you is the database representation used by the daemon. In my opinion, 14 GB isn't that much if you have a decent PC with a decent HDD/SSD. Currently, most of them have plenty of GBs and 14 GB is relatively small compared to that.

[3] If you mean the third party GUIs, that is correct. I think the developers of them will merge LMDB when it is officially released.

Well blockchain.bin is the old one and isn't needed. The DB is ~10GB on Windows currently. Note that a lot of data is duplicated right now, and there is room for more clever optimizations in the future.

LMDB will indeed take memory if it's available, not just during syncing. My working set for example is ~4.5GB right now, but only ~52MB of that is private. The rest is ready to be given to other processes if they need it.

[canth]

So I have fully synchronized with the monero blockchain on 0.9 beta windows.  These are inconsistencies I have noticed:

1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.

2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.

3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.

The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.

Has anyone else running the beta code noticed issues similarly?

I'm not running the windows beta, but in response to #2, that sounds about right: the blockchain is ~14 Gb on my computer.

On a fully synced windows host I get:

File: C:\ProgramData\bitmonero\lmdb\data.mdb
Size: 10.0 GB (10,737,418,240 bytes)

[vvrroomm]

Any monero devs like to comment on this article?  Come on, show us how this is totally wrong.  Make sure to use facts.  Uhh ohh....

What NSA created Cryptonote for:

https://criticl.me/post/what-nsa-created-cryptonote-2292

[XMRpromotions]

If you mean the third party GUIs, that is correct. I think the developers of them will merge LMDB when it is officially released.

LMDB should make development and usability much better for all new features not limited to the GUI.

The amount of work done over the past year has been tremendous. The groundwork performed to date will make things much easier in the future.

[XMRpromotions]

Any monero devs like to comment on this article?  Come on, show us how this is totally wrong.  Make sure to use facts.  Uhh ohh....

What NSA created Cryptonote for:

https://criticl.me/post/what-nsa-created-cryptonote-2292

That is an old article that contains no proof for those allegations. No further comment is necessary. Old news

[vvrroomm]

Any monero devs like to comment on this article?  Come on, show us how this is totally wrong.  Make sure to use facts.  Uhh ohh....

What NSA created Cryptonote for:

https://criticl.me/post/what-nsa-created-cryptonote-2292

That is an old article that contains no proof for those allegations. No further comment is necessary. Old news

Right, and your "supporters" need to pay for the security review by an expert right?  You can't even comment that the article shows that you are liars.  After all being able to find people's private keys is oh so secure. And you are calling Snowden a liar?  You are a liar.

[Cablez]

Well according to multiple explorers I am all synced up and even a block ahead of some, hehe.  So it seems that I do not need the deprecated blockchain.bin any longer with newer versions of the core correct? That will save some space for sure. I guess then you all have another node now up and running.

[MoneroMooo]

Well according to multiple explorers I am all synced up and even a block ahead of some, hehe.  So it seems that I do not need the deprecated blockchain.bin any longer with newer versions of the core correct? That will save some space for sure. I guess then you all have another node now up and running.

That's right, you can safely delete blockchain.bin.

As for the size of the LMDB database, some things are stored more than once, for speed, but some stuff is also wasted, so there is some scope to shrink it a bit. There's other stuff that needs changing in there, so I'm not saying it'll be smaller when all is said and done, but... maybe

The database also uses sparse files. Here, for instance, the logical size of data.mdb is 14 GB, but the actual data is 8 GB. There are "holes" in the file (0 filled preallocated data) that some filesystems use for other stuff, but some don't. I'm not sure whether Windows' filesystem does things cleverly or dumbly there.

[Cablez]

If it is windows then dumbly for sure. lol.  Thanks a lot guys.

[nioc]

Give up guys, this coin is dead!

Only 9 pull requests merged today

[ArticMine]

...
That's right, you can safely delete blockchain.bin.

As for the size of the LMDB database, some things are stored more than once, for speed, but some stuff is also wasted, so there is some scope to shrink it a bit. There's other stuff that needs changing in there, so I'm not saying it'll be smaller when all is said and done, but... maybe

The database also uses sparse files. Here, for instance, the logical size of data.mdb is 14 GB, but the actual data is 8 GB. There are "holes" in the file (0 filled preallocated data) that some filesystems use for other stuff, but some don't. I'm not sure whether Windows' filesystem does things cleverly or dumbly there.

Compressing the .bitmonero directory on Ubuntu GNU/Linux with 7z produces a compressed size of 4.5 GB. The uncompressed size is 14.1 GB. The Windows file system is likely applying some compression on the fly to get the file size down from 14 GB to 8 GB. I am using bitmonero v0.8.8.7-9292c1e.

[digicoin]

Monero is mentioned here https://bitcoinmagazine.com/articles/is-bitcoin-headed-for-a-break-in-fungibility-1450823559

[mmortal03]

Fluffypony interview on Bitcoin Uncensored, starting at 59:54:

https://soundcloud.com/bitcoinuncensored/e20-christmas-poo-122215

lol, I forgot the image to go along with it. That must be it.

[luigi1111]

...
That's right, you can safely delete blockchain.bin.

As for the size of the LMDB database, some things are stored more than once, for speed, but some stuff is also wasted, so there is some scope to shrink it a bit. There's other stuff that needs changing in there, so I'm not saying it'll be smaller when all is said and done, but... maybe

The database also uses sparse files. Here, for instance, the logical size of data.mdb is 14 GB, but the actual data is 8 GB. There are "holes" in the file (0 filled preallocated data) that some filesystems use for other stuff, but some don't. I'm not sure whether Windows' filesystem does things cleverly or dumbly there.

Compressing the .bitmonero directory on Ubuntu GNU/Linux with 7z produces a compressed size of 4.5 GB. The uncompressed size is 14.1 GB. The Windows file system is likely applying some compression on the fly to get the file size down from 14 GB to 8 GB. I am using bitmonero v0.8.8.7-9292c1e.

The Windows one is 10 GB rather than 8, but I think the allocation might happen at a different rate between the two, accounting for 14 GB vs 10.

[TooDumbForBitcoin]

Any monero devs like to comment on this article?  Come on, show us how this is totally wrong.  Make sure to use facts.  Uhh ohh....

What NSA created Cryptonote for:

https://criticl.me/post/what-nsa-created-cryptonote-2292

"...me and a few of my fellow researchers looked at ..."

They did not look at a 5th-grade English grammar text.

Credibility broken.

[medusa13]

who is a miner with more than 10khs?

network hashrate is over 10mhs, so we should sure find some people..

how much do you guys estimate comes from botnets? it has to be somewhere between 70-90% if you ask me.