Pages:
Author

Topic: secp256k1 library and Intel cpu - page 3. (Read 4042 times)

staff
Activity: 4284
Merit: 8808
January 06, 2017, 06:36:11 AM
#5
I thought signature verification was the biggest limiting factor in IBD process (obviously with slow CPU). 
On arm, which doesn't yet use the libsecp256k1 assembly optimizations by default-- perhaps.  Otherwise, no, not since libsecp256k1 made signature validation many times faster. Maybe on some really unbalanced system with a slow single core cpu and huge dbcache and fast network and SSD it might be a majority.
legendary
Activity: 1948
Merit: 2097
January 06, 2017, 06:27:40 AM
#4
Signature verification isn't really the limiting factor in Bitcoin Core performance anymore in any case.

I thought signature verification was the biggest limiting factor in IBD process (obviously with slow CPU). 
staff
Activity: 4284
Merit: 8808
January 06, 2017, 04:41:44 AM
#3
The content in your first link would likely not be helpful.

The content in your second link-- the  would be beneficial, though potentially not by much because the dependency chain in the arithmetic is hand constructed to reduce conflicts.  If someone would like to try them out, it shouldn't be very hard.

In the context of Bitcoin development (thus achows' response), Signature verification isn't really the limiting factor in Bitcoin Core performance anymore in any case.
staff
Activity: 3458
Merit: 6793
Just writing some code
January 05, 2017, 06:41:23 PM
#2
Probably not.
Pages:
Jump to: