Author Topic: [Testnet-StressTest] March 15th - 3:00pm UTC  (Read 4215 times)

0 Members and 1 Guest are viewing this topic.

Offline Customminer

  • Hero Member
  • *****
  • Posts: 623
  • Bitshares FTW!
    • View Profile
  • GitHub: grctest
Re: [Testnet-StressTest] March 15th - 3:00pm UTC
« Reply #15 on: March 26, 2017, 02:13:56 am »

Offline Thom

Re: [Testnet-StressTest] March 15th - 3:00pm UTC
« Reply #16 on: March 26, 2017, 03:57:35 pm »
Thoughts on utilizing a BOINC project to distribute the load generating software required to push the tx/s to new heights? https://steemit.com/beyondbitcoin/@cm-steem/brainstorming-boinc-projects-006#@cm-steem/re-cm-steem-brainstorming-boinc-projects-006-20170326t013749374z

Mentioned the idea on beyondbitcoin #200 too: https://steemit.com/beyondbitcoin/@glitterfart/beyond-bitcoin-radioshow-2017-03-24-gridcoin-raw-recording-for-impatients

What I took away from that conversation is that BOINC would not be suitable for the BitShares testnet to spam the network for testing b/c BOINC projects are geared towards problems where longer term application of CPU resources is required, as opposed to the burst requirements of the testnet. Testing on the testnet is not a continuous, ongoing operation.

I'm not very knowledgeable about BOINC, just commenting on what I heard in the mumble last Friday.
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline Customminer

  • Hero Member
  • *****
  • Posts: 623
  • Bitshares FTW!
    • View Profile
  • GitHub: grctest
Re: [Testnet-StressTest] March 15th - 3:00pm UTC
« Reply #17 on: March 26, 2017, 07:21:43 pm »
Thoughts on utilizing a BOINC project to distribute the load generating software required to push the tx/s to new heights? https://steemit.com/beyondbitcoin/@cm-steem/brainstorming-boinc-projects-006#@cm-steem/re-cm-steem-brainstorming-boinc-projects-006-20170326t013749374z

Mentioned the idea on beyondbitcoin #200 too: https://steemit.com/beyondbitcoin/@glitterfart/beyond-bitcoin-radioshow-2017-03-24-gridcoin-raw-recording-for-impatients

What I took away from that conversation is that BOINC would not be suitable for the BitShares testnet to spam the network for testing b/c BOINC projects are geared towards problems where longer term application of CPU resources is required, as opposed to the burst requirements of the testnet. Testing on the testnet is not a continuous, ongoing operation.

I'm not very knowledgeable about BOINC, just commenting on what I heard in the mumble last Friday.

What I meant was that a Bitshares testnet stress-test BOINC project would be unsuitable for Gridcoin whitelist status as the Gridcoin network focuses on projects with continuous work unit distribution, and the nature of stress-tests is bursty & far apart.

Such a BOINC project is entirely possible, you can distribute any kind of distributed computing application. I'd imagine that for this idea, you would distribute a docker container which contained python dependencies, the testnet stress-test python script, and the bitshares client.

Once running on an user's machine, it would need to create a testnet user account, then the project admin would need to send enough testnet BTS to each participating account, then the main stress-test script would begin bombarding testnet with transactions, so it's not as simple as just distributing the bitshares client and the python script.

With regards to rewarding participating users, you could add an BTS account field within the BOINC profile or within the project registration page, to which you could take into account the credit achieved by participating users during the stress-test phases & distribute an UIA proportionally for their completed work.

Offline Thom

Re: [Testnet-StressTest] March 15th - 3:00pm UTC
« Reply #18 on: March 27, 2017, 04:58:05 pm »
[member=42582]crypto123[/member] thanks for the clarification. I especially like the last part of your idea that provides a way to measure testnet participation.

Sounds like you have the knowledge to put something like that together. If so I encourage you to do so. I've been looking at docker myself, and think that would indeed be a good way to package "an executable unit" to simplify distribution and insure each unit is consistent and behaves the same.
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline Customminer

  • Hero Member
  • *****
  • Posts: 623
  • Bitshares FTW!
    • View Profile
  • GitHub: grctest
Re: [Testnet-StressTest] March 15th - 3:00pm UTC
« Reply #19 on: March 31, 2017, 09:06:33 pm »
I spoke during the 14th Bitshares hangout regarding the potential Bitshares BOINC project for stress-testing, rewarding full/api nodes, testnet experiments, etc.

Unnofficial recording: https://steemit.com/beyondbitcoin/@glitterfart/bitshares-hangout-2017-03-30-beyond-bitcoin-radioshow-raw-recording-for-impatients

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12879
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: [Testnet-StressTest] March 15th - 3:00pm UTC
« Reply #20 on: April 04, 2017, 01:43:18 pm »
The paper that shows some of the end results of the first stress test is available here:
http://docs.bitshares.eu/bitshares/papers/index.html
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline Louis

Re: [Testnet-StressTest] March 15th - 3:00pm UTC
« Reply #21 on: April 04, 2017, 10:33:04 pm »
Thanks Xeroc

Is there a new stress test coming soon?

Offline Brekyrself

  • Hero Member
  • *****
  • Posts: 506
    • View Profile
Re: [Testnet-StressTest] March 15th - 3:00pm UTC
« Reply #22 on: June 21, 2017, 06:29:36 am »
[member=120]xeroc[/member] The conclusion of the paper shows some room for improvement within the network and validator code.  Is this something that can be done with a worker proposal?  EOS appears a ways off so why not improve what we have at the current time?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12879
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: [Testnet-StressTest] March 15th - 3:00pm UTC
« Reply #23 on: June 21, 2017, 09:47:14 am »
[member=120]xeroc[/member] The conclusion of the paper shows some room for improvement within the network and validator code.  Is this something that can be done with a worker proposal?  EOS appears a ways off so why not improve what we have at the current time?
If you can find a developer that wants to get his hands dirty ... funding shouldn't be the problem anymore!
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH