Bitcoin Forum
September 23, 2019, 01:56:00 AM *
News: If you like a topic and you see an orange "bump" link, click it. More info.
 
   Home   Help Search Login Register More  
Pages: « 1 ... 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 [1691] 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 ... 2567 »
  Print  
Author Topic: NXT :: descendant of Bitcoin - Updated Information  (Read 2756163 times)
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 14, 2014, 08:58:27 PM
 #33801

Question: Is it possible to re-use the nxt_db directory when upgrading from 0.7.4 to 0.7.5  without downloading the whole blockchain again?
Yes, it is designed to be possible to upgrade without having to delete the nxt_db directory, that's the reason I bother with applying those SQL statements.

If too slow for Raspberries, do whichever is faster, upgrade or download from scratch.

Did I manage to improve the Raspberry performance with the last release?
Does this mean that we are actually generating checkpoint files on all the nodes all the time? If so, how much work would it be to have newly installed nodes query for the most recent db files and start with that, instead of redownloading the entire blockchain. Of course, must be peer verified checksums, etc.

How fast does the DB grow at 1000TPS?



du says: 257480 for current nxt_db folder
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1569203760
Hero Member
*
Offline Offline

Posts: 1569203760

View Profile Personal Message (Offline)

Ignore
1569203760
Reply with quote  #2

1569203760
Report to moderator
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 14, 2014, 08:58:57 PM
 #33802

Alias assignment being undone? I didn´t touch the client when this message came.
It is not because of something you did. The block that had to be popped off contained an alias assignment transaction. When a block is popped off, an attempt is made to undo all transactions in it. But this type of transaction cannot be undone, and in this case a full rescan of the blockchain is needed.

lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 14, 2014, 09:00:03 PM
 #33803

du says: 257480 for current nxt_db folder
What? Mine is 111M only.

lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 14, 2014, 09:01:49 PM
 #33804

Alias assignment being undone? I didn´t touch the client when this message came.
It is not because of something you did. The block that had to be popped off contained an alias assignment transaction. When a block is popped off, an attempt is made to undo all transactions in it. But this type of transaction cannot be undone, and in this case a full rescan of the blockchain is needed.

Interesting. Why can't this be undone?
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 14, 2014, 09:02:11 PM
 #33805

Does this mean that we are actually generating checkpoint files on all the nodes all the time? If so, how much work would it be to have newly installed nodes query for the most recent db files and start with that, instead of redownloading the entire blockchain. Of course, must be peer verified checksums, etc.
I don't understand what you mean by checkpoint file. The rest is a bad idea.

lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 14, 2014, 09:02:59 PM
 #33806

du says: 257480 for current nxt_db folder
What? Mine is 111M only.

Err:
Code:
pi@raspberrypi ~/nxt $ du -h nxt_db/
252M nxt_db/

Wrong usage of du?
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 14, 2014, 09:03:57 PM
 #33807

Interesting. Why can't this be undone?
Because to find out the previous value of the alias URL, if any, you need to go back through all previous transactions. In effect, again scanning the blockchain.

lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
mikesbmw
Sr. Member
****
Offline Offline

Activity: 339
Merit: 250


View Profile
February 14, 2014, 09:04:20 PM
 #33808

Running 0.7.5:

I get a non-stop list of this:

height 66516 received from vps2.nxtcrypto.org, blacklisting
[2014-02-14 22:01:24.534] DEBUG: Failed to accept block 11979910396361888590 at
height 66516 received from vps2.nxtcrypto.org, blacklisting
[2014-02-14 22:01:26.139] DEBUG: Failed to accept block 11979910396361888590 at
height 66516 received from node3.mynxtcoin.org, blacklisting
[2014-02-14 22:01:27.190] DEBUG: Failed to accept block 11979910396361888590 at
height 66516 received from vps2.nxtcrypto.org, blacklisting
[2014-02-14 22:01:28.239] DEBUG: Failed to accept block 11979910396361888590 at
height 66516 received from vps2.nxtcrypto.org, blacklisting
[2014-02-14 22:01:40.314] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from node3.mynxtcoin.org, blacklisting
[2014-02-14 22:01:41.923] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from node3.mynxtcoin.org, blacklisting
[2014-02-14 22:01:42.979] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from vps2.nxtcrypto.org, blacklisting
[2014-02-14 22:01:44.029] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from vps2.nxtcrypto.org, blacklisting
[2014-02-14 22:01:45.634] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from node3.mynxtcoin.org, blacklisting
[2014-02-14 22:01:46.697] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from vps2.nxtcrypto.org, blacklisting
[2014-02-14 22:01:47.748] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from vps2.nxtcrypto.org, blacklisting
[2014-02-14 22:01:48.810] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from vps2.nxtcrypto.org, blacklisting
[2014-02-14 22:01:50.821] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from node3.mynxtcoin.org, blacklisting
[2014-02-14 22:01:51.923] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from vps2.nxtcrypto.org, blacklisting
[2014-02-14 22:01:53.745] DEBUG: Failed to accept block 12715248329747037589 at
height 66517 received from node90.nxtbase.com, blacklisting


EDIT: okay, seems to have stopped now after several hundred lines of this.

NXT: Next Generation of Cryptocurrency http://nxtcrypto.org
NEM:New Economy Movement http://www.ournem.com/
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 14, 2014, 09:04:39 PM
 #33809

Interesting. Why can't this be undone?
Because to find out the previous value of the alias URL, if any, you need to go back through all previous transactions. In effect, again scanning the blockchain.

Why not caching it?
greyw00lf
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
February 14, 2014, 09:05:23 PM
 #33810

If too slow for Raspberries, do whichever is faster, upgrade or download from scratch.

Did I manage to improve the Raspberry performance with the last release?
copying the db from the old version is definitely faster, because my Raspberry takes a long time to download the whole blockchain (maybe 1h? haven't really watched at the time precisely).

Scanning the blockchain now takes about 9 minutes on my Raspberry.
No issues at the moment with my Pi Smiley even unlocking my account via the GUI is fast now! Thanks Jean-Luc!

ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 14, 2014, 09:06:19 PM
 #33811

If too slow for Raspberries, do whichever is faster, upgrade or download from scratch.

Did I manage to improve the Raspberry performance with the last release?
copying the db from the old version is definitely faster, because my Raspberry takes a long time to download the whole blockchain (maybe 1h? haven't really watched at the time precisely).

Scanning the blockchain now takes about 9 minutes on my Raspberry.
No issues at the moment with my Pi Smiley even unlocking my account via the GUI is fast now! Thanks Jean-Luc!

Have you overclocked your Raspi?
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2128
Merit: 1009

Newbie


View Profile
February 14, 2014, 09:06:23 PM
 #33812

Complexity of signing is O(1).

That is plain wrong. The more bits you have to sign the longer signing takes. The question is: how long in terms of the input length.

We would have O(n) if Sign(32_bytes) == Sign(64_bytes) / 2. Actually we have Sign(32_bytes) == Sign(3200_bytes) / 2, so it's more like O(1). Right?
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 14, 2014, 09:07:45 PM
 #33813

Does this mean that we are actually generating checkpoint files on all the nodes all the time? If so, how much work would it be to have newly installed nodes query for the most recent db files and start with that, instead of redownloading the entire blockchain. Of course, must be peer verified checksums, etc.
I don't understand what you mean by checkpoint file. The rest is a bad idea.


I think he means that nxt.h2.db could be considered a snapshot file.
mcjavar
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
February 14, 2014, 09:09:19 PM
 #33814

Alias assignment being undone? I didn´t touch the client when this message came.
It is not because of something you did. The block that had to be popped off contained an alias assignment transaction. When a block is popped off, an attempt is made to undo all transactions in it. But this type of transaction cannot be undone, and in this case a full rescan of the blockchain is needed.

Thank you for clarification. How can a block "popp off"?
greyw00lf
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
February 14, 2014, 09:12:32 PM
 #33815

du says: 257480 for current nxt_db folder
What? Mine is 111M only.

Err:
Code:
pi@raspberrypi ~/nxt $ du -h nxt_db/
252M nxt_db/

Wrong usage of du?
I have:
Code:
pi@rpi ~/nxt $ du -h nxt_db/
246M nxt_db/
But i always copied the folder from one version to the next... maybe that's why?

greyw00lf
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
February 14, 2014, 09:14:53 PM
 #33816

Have you overclocked your Raspi?
No, i don't know if i will do that, i don't have anything to cool it (no heat sink...) and my pi is in an ordinary plastic-case.

jl777
Legendary
*
Offline Offline

Activity: 1176
Merit: 1090


View Profile WWW
February 14, 2014, 09:15:35 PM
 #33817

Does this mean that we are actually generating checkpoint files on all the nodes all the time? If so, how much work would it be to have newly installed nodes query for the most recent db files and start with that, instead of redownloading the entire blockchain. Of course, must be peer verified checksums, etc.
I don't understand what you mean by checkpoint file. The rest is a bad idea.

It might be a bad idea, but the problem of how will small machines be able to keep up with 1000TPS volumes is unsolved.
checkpoint file would be "entire state of NXT blockchain" at specific intervals. I am assuming you are not storing the entire blockchain now that we have DB,but maybe that is incorrect?

Almost all NXT functions only need the most recent 1440 blocks, so if each machine kept those 1440 blocks locally, they can purge them after that. blockchain FIFO.

As the blockchain grows, it will take longer and longer for initial install. By having the entire state of NXT every hour, or even every day, in a decentralized peer validated form, would allow starting from the most recent hour (or day) and then start processing blocks from that point.

These two are totally independent technically, but combine to allow small raspis to continue forging and being full nodes
If checkpoint files are a bad idea, I can live with that. Is blockchain FIFO a bad idea too?

http://www.digitalcatallaxy.com/report2015.html
100+ page annual report for SuperNET
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 14, 2014, 09:22:43 PM
 #33818

Code:
pi@raspberrypi ~/nxt $ du -h nxt_db/
252M nxt_db/
Wrong usage of du?
No. I guess the database needs vacuuming once in a while. I will do that at shutdown, it means stopping the server will take slightly longer.

lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
greyw00lf
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
February 14, 2014, 09:24:41 PM
 #33819

Thanks! I am reluctant about the overclocking, but I run it with -856xmx ...

What does -856xmx do?

It is the memory available to the jvm, I quoted it wrong:

ps -ax
 2040 ?        SNl   61:45 /usr/bin/java -Xms128m -Xmx856m -jar start.jar STOP.PORT=7873 STOP.KEY=0815


-Xms128m is the minimum that is reserved at the start, and -Xmx856m is the maximum it can have, in megabytes. I often had crashes with a maximum smaller 450MB, but with giving it almost all the memory, it runs quite good.

Except that dl'ing the whole blockcahin is quite some venture.
i use -Xms320m -Xmx480m
how can you give it 856m? Don't you have a pi with 512MB? Or are you using swap? Or an other device?

Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 14, 2014, 09:25:43 PM
 #33820

Thank you for clarification. How can a block "popp off"?
With a little help from a stronger block that kicks him out Smiley

Only one block can be at the end of the chain, but multiple nodes try to generate blocks at the same time. The better one wins, if the other was attached first it gets popped off.

lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
Pages: « 1 ... 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 [1691] 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 ... 2567 »
  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!