Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blocksci_parser - stuck #26

Closed
pranay01 opened this issue Dec 13, 2017 · 5 comments · Fixed by #27
Closed

blocksci_parser - stuck #26

pranay01 opened this issue Dec 13, 2017 · 5 comments · Fixed by #27

Comments

@pranay01
Copy link

pranay01 commented Dec 13, 2017

I ran the following command with correct coin data directory,

blocksci_parser --coin-directory .bitcoin --output-directory bitcoin-data

But the parser is not giving any output or indications of processing. Also size of bitcoin-data folder is not increasing? How long does the parsing take - and why is it not giving any processing indication?

Also, does blocksci_parser only work if we have complete chain data?

@shihao-guo
Copy link

if you use top or htop you will see the cpu and memory use of the process, which gives you some processing indications.

@pranay01
Copy link
Author

pranay01 commented Dec 14, 2017

I see blocksci_parser working in htop. But it takes only 0.7% CPU and 228MB memory. I have a system which has a RAM of 6.8 GB.

When I try to import it in python3.5 , it gives a segmentation fault.
`
Python 3.5.2 (default, Nov 23 2017, 16:37:01)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.

import blocksci
chain = blocksci.Blockchain("/mnt/disk1/blocksci_data")
Segmentation fault (core dumped)
`

@hkalodner hkalodner reopened this Dec 15, 2017
@hkalodner
Copy link
Collaborator

hkalodner commented Dec 15, 2017

Hi @pranay01,

The segmentation fault is from the python module is likely due to corruption of some sort in the data located at /mnt/disk1/blocksci_data. The code is still fairly research quality so it doesn't handle the unexpected very well 😄

Have you tried the new release of BlockSci that we released yesterday? It should provide feedback through the entire process. If I remember correctly, the previous version didn't provide feedback during the initial block header parsing stage. Now all stages should provide percentage done estimates.

The full parse process takes a little under a day at this time. The many data processing takes about 8 hours and then there is a long index generation process. BlockSci doesn't require complete chain data and the parser in fact has a --max-block parameter that lets you process only up to a given block height.

@will-holley
Copy link

@hkalodner - Is the data set you are using in development publically available?

@hkalodner
Copy link
Collaborator

I'm not exactly sure what you mean by data set. BlockSci's data is generated directly from raw blockchain data. The readme links to an EC2 AMI which has a BlockSci instance running on it which contains the full Bitcoin blockchain as of a couple days ago. Additionally the data can be generated on any machine running a Bitcoin full node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants