14:49:01 <selsta> slave_blocker2: so what are you suggesting? it's not clear for the user that a transaction is being created and it appears hung?
14:49:33 <slave_blocker2> correct
14:49:34 <selsta> just trying to figure out if it's a bug or if you are suggesting that it's a bad user experience
14:50:01 <selsta> can you try a remote node? for example 88.198.199.23:18081 (hosted by me)
14:50:11 <selsta> I'm curious how long it takes to create a tx with that node
14:50:27 <slave_blocker2> i am assuming its both
14:50:34 <selsta> it should not take 20 seconds
14:50:54 <slave_blocker2> thats not the point
14:51:15 <slave_blocker2> i always use the cli and not the gui.
14:51:22 <selsta> ??
14:51:41 <selsta> didn't suggest a gui
14:52:16 <selsta> I mean can you try the remote node with the CLI wallet to see if it's an issue with your local node
14:52:22 <slave_blocker2> and whenever i have done a tx in the past after i do transfer addr amount, hit enter it hangs
14:52:35 <slave_blocker2> for about 20 secs
14:52:49 <slave_blocker2> and is unresponsive to ctrl+c.
14:53:09 <nioc> I thought that it was normal that it takes 20 seconds to construct a tx
14:53:29 <slave_blocker2> in the past when i was using a hdd, it was so bad that i had to try 2 or 3 attempts to make the tx.
14:53:30 <selsta> mine never take 20 seconds, but maybe that's different if you have hundreds of outputs
14:54:20 <slave_blocker2> no
14:54:50 <slave_blocker2> just 2 outputs
14:55:14 <selsta> and how many inputs?
14:55:29 <slave_blocker2> just one
14:55:46 <selsta> well in that case it takes like 1 second on my system
14:56:16 <selsta> that's why I want you to test a different node so that we can figure out if it's a node or a client issue
14:56:24 <slave_blocker2> but you are running the monerod and the cli on the same pc?
14:56:29 <selsta> no
14:57:23 <slave_blocker2> well i was using two local pcs one with an ssd...
14:58:00 <moneromooo> If the daemon was just started, it will take a while to gather the histogram of per block rct outs, which the wallet requests to pick fake outs. This might well be what you are seeing.
14:58:32 <slave_blocker2> hum
14:58:47 <slave_blocker2> no the daemon is running all the time.
14:58:58 <moneromooo> If reading off your db is slow, the daemon will take a while. This is heavy operation. You can tell whether this is the reason by attaching gdb to the daemon process: gdb build/.../bin/monerod `pidof monerod`; thread apply all bt
14:59:05 <slave_blocker2> i dont have xmr now at hand to do the tx im sorry
14:59:27 <moneromooo> OK, then it's not that. If you try again and it blocks again, try these:
14:59:55 <moneromooo> top   # and check what process is taking CPU or I/O time - likely monerod
15:00:04 <moneromooo> gdb build/.../bin/monerod `pidof monerod`; thread apply all bt
15:00:09 <moneromooo> gdb build/.../bin/monero-wallet-cli `pidof monerod`; thread apply all bt
15:00:20 <moneromooo> The last two will print lots of text, paste to paste.debian.net
15:00:52 <moneromooo> A snapshot of the top output might also help. For instance if your wa% is high (which means it's busy waiting on disk).
15:01:43 <slave_blocker2> ok thanks i will try that
15:01:46 <moneromooo> "sudo perf top" would also be useful for a 20 second delay. Run this right after it starts hanging.
15:01:57 <moneromooo> If you're on linux only though.
15:02:03 <slave_blocker2> yes
15:02:30 <moneromooo> Also paste the perf output to paste.debian.net.
15:02:37 <slave_blocker2> so what does happen after i do transfer addr amount, hit enter ?
15:02:46 <moneromooo> If deamon and wallet aren't on the same machine, run it on both. 
15:02:57 <moneromooo> Lots of things!
15:03:32 <moneromooo> And hte above will help zero in on the thing that's causing you trouble.
15:03:32 <slave_blocker2> well im checking the cpu monitor on the cli machine and its idle
15:03:44 <moneromooo> While it's waiting ?
15:03:52 <slave_blocker2> so i am assuming that the fee is given by the daemon
15:04:29 <slave_blocker2> yes
15:05:11 <slave_blocker2> i hit transfer addr amount, and hangs look at monitor in xubuntu seams not doing anything
15:05:17 <moneromooo> s/waiting/stuck/
15:05:49 <moneromooo> Then try it on the daemon side.
15:05:54 <ocb> selsta: sometimes it takes ~2 minutes to construct a transaction for me, this was mostly on old hardware laptops, dual core with 2gb memory. on newer hardware (i7-3xxx) it takes some time to construct the tx ~10-30 seconds, with 1-2 inputs 2 outputs. althought i have not sent a monero transaction for a while so cant remember how was it last time, but im sure its not 1 second, more like 15-20.
15:05:55 <slave_blocker2> well when it hangs i enter into total dispair the cli could tell me why its waiting
15:06:02 <slave_blocker2> the user is like huh
15:06:58 <slave_blocker2> yes the cli is running on a x5460
15:07:32 <slave_blocker2> the deamon is running on an i3 655
15:07:37 <slave_blocker2> or something
15:08:14 <ocb> selsta: it was through cli using remote rpc full node running on 2xE5-2650/64G memory. but i dont mind much, just find it awfully slow when construction transaction on a low resource virtual machine, takes more than 2 minutes. /away
15:09:26 <slave_blocker2> this is not something that is awfull and bad
15:10:11 <slave_blocker2> i see it as a poor user experience that probably could be fixed with some new upgrade.
15:10:33 <selsta> ocb: just tested it with a timer, a sample transaction took ~1 second with my remote node
15:10:35 <slave_blocker2> like afrter hit transfer addr amount,
15:10:49 <selsta> so I'm a bit surprised that you regularly see 20 seconds :D
15:11:03 <slave_blocker2> the user gets info like "gathering fee info"
15:11:15 <moneromooo> Reticulating splines...
15:11:34 <slave_blocker2> then "gathering decoys"
15:11:47 <moneromooo> "Waiting for your incredibly slow disk (what is that, MFM ?)"
15:11:48 <slave_blocker2> lol
15:11:51 <slave_blocker2> what
15:12:37 <moneromooo> Anyway, you might have missed "< moneromooo> Then try it on the daemon side."
15:12:52 <moneromooo> And do check for I/O load on both.
15:13:01 <moneromooo> (in addition to CPU load)
15:13:20 <moneromooo> That's the "wa" column.
15:13:21 <slave_blocker2> i will copy your commands and try it for next time.
15:13:27 <moneromooo> OK
15:13:35 <slave_blocker2> thanks so much
15:13:53 <slave_blocker2> :)
15:57:02 <crd716> How's everyone doing?
15:59:41 <raecarruth> watching crd716 ask redundant questions....
16:00:40 <crd716> cool
23:26:40 <Wolf0> I *like* the XMR Art Fund! https://twitter.com/XMRArtFund/status/1474787942673489924