MetacoSA / QBitNinja

An Open Source and powerful blockchain API
MIT License
68 stars 42 forks source link

which server would you advise? #86

Open jrmaciel opened 5 years ago

jrmaciel commented 5 years ago

my server is very slow, do you advise with more memory or processing? the qbit console is overloading, I currently have an A2m_v2

NicolasDorier commented 5 years ago

You mean for the indexer part? I don't know, check the task manager to see what is the bottleneck.

jrmaciel commented 5 years ago

Yes, he is consuming too much.

img_2122

jrmaciel commented 5 years ago

my server have 16 of memory and 2 processors

NicolasDorier commented 5 years ago

Are you indexing step or it is like this after indexed everything?

jrmaciel commented 5 years ago

this is so after you have indexed everything

NicolasDorier commented 5 years ago

Does it works? Is it indexing blocks correctly?

jrmaciel commented 5 years ago

yes it is working, the only problem is the lack of memory and then it causes the processes to be slow

which server do you use in api.qbit.ninja?

NicolasDorier commented 5 years ago

I used Standard D1 v2 (1 vcpus, 3.5 GB memory)

image

NicolasDorier commented 5 years ago

I noticed that putting bitcoin core on the OS drive speed up things a lot.

NicolasDorier commented 5 years ago

The CPU is mainly unused on my side and not too much memory is taken. Maybe is it the console logs. Try to run it via the Task Scheduler.

NicolasDorier commented 5 years ago

You need to run "even if not logged in" on Task scheduler so the console does not show up.

jrmaciel commented 5 years ago

I created 2 files start c:/"Program Files"/Bitcoin/daemon/bitcoind -datadir=f:/Bitcoin and

start C:\Users\jnrmcl\Documents\QbitFinal\QBitNinja-master\QBitNinja.Listener.Console\bin\Release\net471\QBitNinja.Listener.Console.exe --listen

jrmaciel commented 5 years ago

but still the memory remains very high this is how it is not indexing right

NicolasDorier commented 5 years ago

As I said, the CPU problem is probably just transaction ids printing. Use the task scheduler so QBitNinja indexer run without printing output to a console.

jrmaciel commented 5 years ago

after running in output to a console my balance has a problem look

https://btccmd.azurewebsites.net/balances/1P8tS7wZ2qn9JkCf48GVkkqovXR3y3kmTm/summary

http://api.qbit.ninja/balances/1P8tS7wZ2qn9JkCf48GVkkqovXR3y3kmTm/summary

jrmaciel commented 5 years ago

the problem was in my web application, the only problem now that shows the new transactions but the balance is problem

jrmaciel commented 5 years ago

restart qbit pls, I'm using it while I work on my

jrmaciel commented 5 years ago

I think I had a problem with the indexer.

I did --cancelinit and then --init again

NicolasDorier commented 5 years ago

Why restart? it is working.

For the difference of values, did the initial indexing really finished? It takes several days.

jrmaciel commented 5 years ago

why I try to get a balance or something and it's not updated and also when I try to send a transaction it takes about 25 minutes to send in http://api.qbit.ninja

this is only while I finish indexing my server again

jrmaciel commented 5 years ago

yes it was over, it was working but I think it gave some problems in the blocks and it did not update the balances correctly. he just pulled 135 queue, I think the blocks that gave problem