ok i managed to convert on windows 7 x64 with batch size 1000 using blockchain_converter. was really fast(maybe 30min), but:
- data.mdb uses now more than 16gb, this is not normal no? this looks like some crazy pre allocation. same happens when exporting / importing.
- i want to highlight again, on windows monero uses now %programData% as default location instead of %appData% like in 0.8.8.6.
i am fully synced right now and bitmonerod uses 31 Megabyte of ram
good job devs !!!
yeah, thats the size of my data.mdb. Fluffypony said it something with windows not liking sparse files. Whatever that means.
weird - I think my data.mdb was in %appData%/bitmonerod/LMDB , not %programData%, but I'll double check when I get home.
It was %programdata% for me, too.
Btw, GingerAle, I've discovered a problem with running the latest binaries with MoneroX: the bitmonerod process doesn't close when exiting MoneroX. I see in the log that it *does* receive a stop signal from MoneroX, and p2p net loop does eventually stop, but the daemon process doesn't close.
I assumed that MoneroX just hasn't been updated to use the current RPC commands to stop the daemon, but...
I tried running the stop_daemon command myself from the command line, outside of MoneroX, but that also doesn't seem to work. It works just fine if I've run bitmonerod myself, so I know I'm doing it right.
I can't tell if bitmonerod after closing MoneroX is just stuck in some buggy state, or if there is some sort of process communication issue that isn't obvious to me. It doesn't seem to be a permissions issue, as the process shows up as loaded by my username in Windows in both instances. I can still get the local block height while it is in this state, and the daemon state *is* detected when running stop_daemon, exit, and fast_exit from the command line in various combinations, so I know that the communications are being received by it to some extent... the process just doesn't close.
