Was wondering how many transaction i can sign per second

[xinzark]

I have been thinking about doing a stress test to a bitcoin fork whose fees are low
*Not talking about bcash here

Not the type of stress test that checks how many transaction the network can handle but how many transaction i can sign per second using a 2 vCpu and 4GB ram vps
I want to do 10k transaction and see how long it takes to complete

Edit : Will be using vultr $20 VC2 instance

[1713865217]

1713865217

[1713865217]

1713865217

[1713865217]

1713865217

[xinzark]

have anyone done this before ?

[bob123]

How is this related to a stress test ?
You aren't stress testing anything besides your own hardware with mass signing transaction.

That's like saying: "I am going to stress test the post office by writing 100 words per minute".
If you do not send those mass letters (transactions), you aren't stress testing anything (besides yourself)
.

If you really want to test something, you'll need to actually test the network. Not your own hardware.

[xinzark]

How is this related to a stress test ?
You aren't stress testing anything besides your own hardware with mass signing transaction.

That's like saying: "I am going to stress test the post office by writing 100 words per minute".
If you do not send those mass letters (transactions), you aren't stress testing anything (besides yourself)
.

If you really want to test something, you'll need to actually test the network. Not your own hardware.

Yeah i know that
let's say a 2cpu hardware processes 10tx/sec, then a 4cpu and 8cpu will process 15tx or 18tx per sec
getting better hardware doesn't always mean it would yield better results, even if it does then it would be fractional

2cpu and 4gb ram is a pretty standard amount of resources for a node

[bob123]

But what are you trying to stress test ?

If you are trying to stress test other nodes (which is illegal if you don't have the permission) it is irrelevant how fast you can sign transaction.
You could simply broadcast them all at once, regardless whether it took you 1 or 100 minutes to create them.

What you are going to do is more like a benchmark of your own hardware, than a stress test of anything else.


What are you trying to accomplish with your test ? What do you want to test ?

[Theb]

What are you trying to accomplish with your test ? What do you want to test ?

That is what I am also wondering, I see no point of stress testing your hardware when it comes to signing transactions, this problem won't even be a problem if you know what you are trying to achieve. If you want a real benchmark to happen on your hardware you can try out Cinebench and 3dmark in order for you to compare your scores to other people, these two are one of the leading benchmark tools when it comes to measuring your pc's power.

[xinzark]

so many sig spammers

[jackg]

so many sig spammers

I think you’re trying to stress test your vps?

But I’m equally as clueless as everyone else is as to why you’d possibly want to, what’s it going to do? Say you sign 10txs per sec here and then it rises once the instance gets more ram... 

Also, what operating system is it, what client are you using? I’m sure there’s a python bitcoin library that will preform a lot differently than bitcoin cores one for example. Maybe you’re trying to test the fastest client or something but until you give us that we will all be stuck.

If people don’t reply the way you want you’re usually on the marketplace or the alt section not tech support.

[pooya87]

the time it takes to sign a transaction depends on these:
1. script. to put simply with an example transaction requiring multi signature would take longer since you have to sign it multiple times with multiple keys.
2. your hardware. and how much of it you are using. for instance whether you are using CPU or GPU and whether you are using 1 core or multiple,...
3. the cryptography method that the coin is using. it is not always elliptic curve and it is not always the same elliptic curves. different methods have different times. also among ECs they are not all using the same curve. those using 256 bit curves will have 256 bit keys and your calculations will be done on that size numbers. a bigger curve like the 521 ones will take longer and the smaller curves like 192 and 224 bit curves will be faster. i believe one of the bitcoin forks changed the cryptography while talking about post quantum computer thing so that is something to consider.
4. the code that you are using for signing. there is not only one method of signing using Elliptic Curve. there are multiple ones and also depending on how they are coded it can take longer or faster to create a signature. for instance libsec256k1 is super fast but other libraries such as using openSSL is much slower.

p.s. as others said you are not stress testing the coin, you are bench-marking your hardware with the conditions i mentioned above.

[xinzark]

the time it takes to sign a transaction depends on these:
1. script. to put simply with an example transaction requiring multi signature would take longer since you have to sign it multiple times with multiple keys.
2. your hardware. and how much of it you are using. for instance whether you are using CPU or GPU and whether you are using 1 core or multiple,...
3. the cryptography method that the coin is using. it is not always elliptic curve and it is not always the same elliptic curves. different methods have different times. also among ECs they are not all using the same curve. those using 256 bit curves will have 256 bit keys and your calculations will be done on that size numbers. a bigger curve like the 521 ones will take longer and the smaller curves like 192 and 224 bit curves will be faster. i believe one of the bitcoin forks changed the cryptography while talking about post quantum computer thing so that is something to consider.
4. the code that you are using for signing. there is not only one method of signing using Elliptic Curve. there are multiple ones and also depending on how they are coded it can take longer or faster to create a signature. for instance libsec256k1 is super fast but other libraries such as using openSSL is much slower.

p.s. as others said you are not stress testing the coin, you are bench-marking your hardware with the conditions i mentioned above.

thanks for the answer