doppelgnubeard has quit [Ping timeout: 276 seconds]
doppelgnubeard has joined #stellar-dev
doppelgnubeard has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
acetakwas has joined #stellar-dev
acetakwas has quit [Max SendQ exceeded]
acetakwas has joined #stellar-dev
acetakwas has quit [Max SendQ exceeded]
acetakwas has joined #stellar-dev
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
acetakwas has quit [Max SendQ exceeded]
acetakwas has joined #stellar-dev
acetakwas has quit [Ping timeout: 244 seconds]
acetakwas has joined #stellar-dev
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
<stellar-slack>
<illya> hi, would like to get more info about - stellar performance -setting up private nets Any references please ?
<stellar-slack>
<illya> thx
<stellar-slack>
<bartek> for performance, I think the most recent tests resulted in ~70 tx/second and ~500 operations / second. to create a private network simply change network passphrase in your stellar-core config file, setup some nodes, and start the network with --force-scp switch. we don't have a doc about this yet but hopefully other slack members can help you.
<stellar-slack>
<illya> @bartek: thx
acetakwas has quit [Ping timeout: 248 seconds]
acetakwas has joined #stellar-dev
<stellar-slack>
<jed> that is performance on a very small box. with ssd the performance is ~4000 ops/sec
acetakwas has quit [Ping timeout: 252 seconds]
acetakwas has joined #stellar-dev
doppelgnubeard has joined #stellar-dev
doppelgnubeard has quit [Ping timeout: 276 seconds]
<stellar-slack>
<jed> bartek: in go-stellar-base there is now the horizon package and response as a sub package of that. But is that necessary? As a user it seems better to be using `horizon.Account` rather than `response.Account` the first is more clear it is stellar related.
acetakwas has quit [Ping timeout: 252 seconds]
doppelgnubeard has joined #stellar-dev
doppelgnubeard has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
doppelgnubeard has joined #stellar-dev
<stellar-slack>
<bartek> @jed I can move it if you want. the reason why I put it in a separate package is that they are copied directly from horizon (more explanations here: https://github.com/stellar/go-stellar-base/pull/22#issuecomment-203971309) and developers don't really need to use `response.Account` as there is no need to create this objects outside of the library.
doppelgnubeard has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<stellar-slack>
<jed> bartek but LoadAccount returns a response.Account so people will have to interact with it right?
<stellar-slack>
<bartek> yes, I meant they don't need to use the type name directly: ``` response, err := horizon.LoadAccount("...") ```
<stellar-slack>
<jed> I don't think you can assume that. They might be storing them or something
<stellar-slack>
<bartek> I don't have a preference. I will move it level up.
<stellar-slack>
<jed> scott do you have an opinion?
<stellar-slack>
<scott> I’m fine with moving it all into the horizon package.