<stellar-slack>
<matschaffer> developer FYI: stellar-core testnet will get a history reset just as soon as I get the new key format sorted out. Will update here with new keys once the main work is complete. Documentation updates with new keys will follow.
loopy has joined #stellar-dev
<stellar-slack>
<matschaffer> stellar-core testnet update complete. Starting on horizon now
<stellar-slack>
<matschaffer> New keys are ``` core-testnet-001: 'GDKXE2OZMJIPOSLNA6N6F2BVCI3O777I2OOC4BV7VOYUEHYX7RTRYA7Y' core-testnet-002: 'GCUCJTIYXSOXKBSNFGNFWW5MUQ54HKRPGJUTQFJ5RQXZXNOLNXYDHRAP' core-testnet-003: ‘GC2V2EFSXN6SQTWVYA5EPJPBWWIMSD2XQNKUOHGEKB535AQE2I6IXV2Z’ ```
de_henne_ has joined #stellar-dev
pixelbeat_ has quit [Ping timeout: 240 seconds]
de_henne has quit [Ping timeout: 264 seconds]
<stellar-slack>
<lab> :thumbsup:
<stellar-slack>
<lab> I tried horizon but failed
<stellar-slack>
<lab> $ curl https://horizon-testnet.stellar.org/accounts/GCEZWKCA5VLDNRLN3RPRJMRZOX3Z6G5CHCGSNFHEYVXM3XOJMDS674JZ { "type": "server_error", "title": "Internal Server Error", "status": 500, "detail": "An error occurred while processing this request. This is usually due to a bug within the server software. Trying this request again may succeed if the bug is transient, otherwise please report this issue to th
<sacarlson>
@lab maybe that last core reset broke it
sv-logger has quit [Remote host closed the connection]
sv-logger has joined #stellar-dev
<stellar-slack>
<lab> i saw no commit of go-horizon for strKey stuff, correct me if i missed.
<sacarlson>
@lab looks like he said starting on horizon but didn't complete?
<stellar-slack>
<lab> and did anyone tested loadgen else?
<stellar-slack>
<lab> i tested a single node with forcescp
<stellar-slack>
<lab> start with "--c generateload?accounts=10000000&txs=50000000&txrate=auto"
<stellar-slack>
<lab> stellar-core crashed 2/2 times around creating 10k accounts.
<sacarlson>
as of late only thing I've done was create a funded working account from my own running core. I'm not using horizon yet. direct to core with ruby-stellar-core
<stellar-slack>
<matschaffer> @lab: I can’t get horizon to re-fund friendbot
<stellar-slack>
<matschaffer> gonna leave it off until scott has a chance to see what’s up
<sacarlson>
glad to see you guys giving status of what you see
<stellar-slack>
<lab> scala, a jvm-base language. http://scala-lang.org|scala-lang.org
<sacarlson>
ok cool
<stellar-slack>
<matschaffer> lab: we use generateload in the delivery pipeline, though not in auto mode, and with a smaller set of accounts
<stellar-slack>
<meetreks> scala is the new Java
<stellar-slack>
<meetreks> Hi, wondering if someone from stellar can help meetreks [3:27 PM] Suppose If I want to find the best rate for my payment transfer meetreks [3:28 PM] will static_path_find help me with that?
<stellar-slack>
<lab> what your average txs? highest of mine is 20 tx/s
<stellar-slack>
<lab> meetreks, try new network. static_path_find if obsoleted
<stellar-slack>
<lab> matschaffer, did andrew quit from SDF? why nobody mentioned it.
<sacarlson>
@meetreks and as far as the old path, I think I've seen it well explained in the ripple docs that is as I assume stellard is just a clone of it
<stellar-slack>
<lab> s/if/is
<stellar-slack>
<matschaffer> lab: pretty sure we’re running at 20tx/s as well. `generate_load_and_await_completion 2000, 2000, 20` in the stellar_core_commander recipe
<sacarlson>
@meetreks and from what I read it sounds like what I explained before was correct
<stellar-slack>
<matschaffer> meetreks: pretty sure I’m the only one online and I have no idea how static_path_find works, sorry about that
<stellar-slack>
<matschaffer> but lab is right that old network stuff is deprecated, which is why I haven’t spent any time learning it (beyond how to stand it up when it falls over). And yes it’s basically ripple
<stellar-slack>
<matschaffer> dev FYI update: testnet horizon is offline for the time being. Will update when it’s back online
<stellar-slack>
<lab> jed and graydon said about 1k tps and i miss the trick.
<stellar-slack>
<graydon> we tried to design all components to be able to sustain that sort of rate on paper. in practice it doesn't run that fast yet.
<stellar-slack>
<graydon> though I had it sustaining over 120 tps on my workstation single-node config yesterday without breaking a sweat (like load avg. 0.2)
<stellar-slack>
<lab> i remember you said something about a test on you laptop, but i forgot the origin, twitter or somewhere?
<stellar-slack>
<graydon> I mean there's an auto-load mode in the current distribution ("stellar-core --test [autoload]") that scales up the tx rate gradually until ledger close latency is 250ms
<stellar-slack>
<graydon> but that doesn't really represent "load" in a terribly scientific sense, just a very safe lower bound
<stellar-slack>
<lab> did you consider offload crypto calculations to other cores?
<stellar-slack>
<graydon> it's unlikely to be necessary. even without any caches the crude verify speed of ref10 ed25519 is about 5000 verifies/sec
<stellar-slack>
<graydon> signature verification isn't really a bottleneck unless we do too many due to repeated / non-cached verification (as we were two days ago)
<stellar-slack>
<lab> i didn't investigate the metrics and just got the idea when saw your "verification cache" commit.
<stellar-slack>
<graydon> at the moment the latency bottleneck seems to be that db roundtrips (with postgres) are a bit slow. literally communication latency through tcp. userspace CPU isn't terribly busy.
<stellar-slack>
<lab> right, i was also strange about the low tps and low cpu load
<stellar-slack>
<graydon> yeah. so cutting roundtrips is the first step and it seemed to help quite a bit. I'll get back at it once the remaining acceptance tests are passing.
<stellar-slack>
<lab> fyi, i tested with sqlite3 in win7
<stellar-slack>
<graydon> but the other concern is that scp itself might take time to converge on consensus / flood txs around, and this might not scale ideally with more nodes. we'll have to see.
<stellar-slack>
<graydon> can you get a stacktrace on the crash? tbh I haven't been doing [autoload] on windows, haven't been on windows in a while. mostly jed and nicolas do windows, though I have a machine around I can use if need be.
<stellar-slack>
<lab> it's based commit 06f289de after removing some asserts
<stellar-slack>
<lab> now stacktrace yet and i will try to solve it. jed and nicolas may have no same env as me.
<stellar-slack>
<lab> I build the stellar-core in release mode by my qt build script with TDM-GCC-64
<stellar-slack>
<lab> s/now/no
<stellar-slack>
<graydon> TDM! there's a name I've not heard in a while :)
<stellar-slack>
<graydon> we build and test on windows with msvc; I haven't tried it under mingw in a long time
TheSeven has quit [Ping timeout: 244 seconds]
TheSeven has joined #stellar-dev
de_henne_ has quit [Remote host closed the connection]
de_henne has joined #stellar-dev
koolhead17 has joined #stellar-dev
<stellar-slack>
<meetreks> Hi
<stellar-slack>
<meetreks> simple query which i will be really glad if I can get some help
<stellar-slack>
<meetreks> static_path_find
<stellar-slack>
<meetreks> does it return me the best path and best rate?
<stellar-slack>
<meetreks> if the answer is Yes, how does it work?
<stellar-slack>
<dzham> in old stellar: 1) yes. 2) magic
<stellar-slack>
<dzham> depends on your definition of “best”, btw
<stellar-slack>
<meetreks> @dzham:
<stellar-slack>
<meetreks> Can you explain me this
<stellar-slack>
<meetreks> If I use static_path_find
<stellar-slack>
<meetreks> what is the role of the issuer there?
<stellar-slack>
<dzham> you mean in destination_amount?
<stellar-slack>
<meetreks> no
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack>
<meetreks> Well sorry
<stellar-slack>
<meetreks> Yes
<stellar-slack>
<dzham> so you’re not talking about the static_path_find parameters
<sacarlson>
I saw other docs on ripple but forget what I was reading
<sacarlson>
didn't save the links
<stellar-slack>
<meetreks> Let me show what I have got for the last 6 months
<stellar-slack>
<meetreks> var rpc = require('node-json-rpc'); var xmlParser = require('js2xmlparser'); exports.callBack = function(){}; var options = { host: '10.241.60.41', port: 6050, path: 'http://s1.ripple.com:51234', strict: true }; // Create a server object with options var client = new rpc.Client(options); exports.getRipplePathFindResponse = function (filename,sourceAcc, destAcc, is
<stellar-slack>
<meetreks> var fs = require('fs'); var destAmount; var sourceCurr; var destCurr; var row = 0; var rawData; var responseReceived; var sourceAccount = "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59"; var destAccount = "ra5nK24KXen9AHvsdFTKHSANinZseWnPcX"; var issuer = "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"; var response = require('./ripplepathfind.js'); var fileName = "ResponseXMLOutput"; var rpc = require('node-json-rpc'); var xml
<stellar-slack>
options = { host: '10.241.60.41', port: 6050, path: 'http://s1.ripple.com:51234', strict: true }; // Create a server object with options var client = new rpc.Client(options); fs.readFile('C:\\CRISP\\Engine Source\\TransactionFile\\transaction.txt', 'utf8', function (err, data) { if (err) { return console.log(err); } rawData = data; response.callBack = fs.callRem
<stellar-slack>
destCurr + '::' + destAmount ); var result = response.getRipplePathFindResponse(fileName,sourceAccount, destAccount, issuer, sourceCurr, destCurr, destAmount,row); ++row; } };
<stellar-slack>
<meetreks> I have been trying and it does not find me the path at all
<sacarlson>
well my software returned a path as I must have shown you
<sacarlson>
It's not java it's ruby
<sacarlson>
oh and that's ripple
<sacarlson>
I"ve never pointed at ripple
<sacarlson>
you would need to have a view of the books to have an idea what to expect to see in path I would think.
<stellar-slack>
<meetreks> I did, and no paths were returned
<sacarlson>
no path in the books? are there any open orders?
<stellar-slack>
<meetreks> so wondering if someone really saw a path returned from stellar by just mentioning source and destination
<stellar-slack>
<dzham> you’d need destination_amount as well, but yeah, I’ve had static_path_find running since, hmm, ages
<stellar-slack>
<meetreks> @dzham, did it return you any active path?
<sacarlson>
yes I ran it also and found a path return if I put in an amount that I knew was on the books. if I went outside what I knew was for sale no path was returned
<stellar-slack>
<meetreks> so you populated an issuer is it?
<sacarlson>
yes I created a simulated market
<stellar-slack>
<meetreks> :)
<sacarlson>
I gave you the tools to expand opon it
<stellar-slack>
<dzham> oh, yeah. I’ve only really done one or two currency tx’s on http://launch.stellar.org|launch.stellar.org, all others I’ve submitted myself
<stellar-slack>
<meetreks> can you do a prepare payment and see if it returns the path?
<sacarlson>
prepare payment? I setup orders to buy and sell