slave_blocker2: so what are you suggesting? it's not clear for the user that a transaction is being created and it appears hung?

correct

just trying to figure out if it's a bug or if you are suggesting that it's a bad user experience

can you try a remote node? for example 88.198.199.23:18081 (hosted by me)

I'm curious how long it takes to create a tx with that node

i am assuming its both

it should not take 20 seconds

thats not the point

i always use the cli and not the gui.

??

didn't suggest a gui

I mean can you try the remote node with the CLI wallet to see if it's an issue with your local node

and whenever i have done a tx in the past after i do transfer addr amount, hit enter it hangs

for about 20 secs

and is unresponsive to ctrl+c.

I thought that it was normal that it takes 20 seconds to construct a tx

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.

mine never take 20 seconds, but maybe that's different if you have hundreds of outputs

no

just 2 outputs

and how many inputs?

just one

well in that case it takes like 1 second on my system

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

but you are running the monerod and the cli on the same pc?

no

well i was using two local pcs one with an ssd...

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.

hum

no the daemon is running all the time.

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

i dont have xmr now at hand to do the tx im sorry

OK, then it's not that. If you try again and it blocks again, try these:

top # and check what process is taking CPU or I/O time - likely monerod

gdb build/.../bin/monerod `pidof monerod`; thread apply all bt

gdb build/.../bin/monero-wallet-cli `pidof monerod`; thread apply all bt

The last two will print lots of text, paste to paste.debian.net

A snapshot of the top output might also help. For instance if your wa% is high (which means it's busy waiting on disk).

ok thanks i will try that

"sudo perf top" would also be useful for a 20 second delay. Run this right after it starts hanging.

If you're on linux only though.

yes

Also paste the perf output to paste.debian.net.

so what does happen after i do transfer addr amount, hit enter ?

If deamon and wallet aren't on the same machine, run it on both.

Lots of things!

And hte above will help zero in on the thing that's causing you trouble.

well im checking the cpu monitor on the cli machine and its idle

While it's waiting ?

so i am assuming that the fee is given by the daemon

yes

i hit transfer addr amount, and hangs look at monitor in xubuntu seams not doing anything

s/waiting/stuck/

Then try it on the daemon side.

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.

well when it hangs i enter into total dispair the cli could tell me why its waiting

the user is like huh

yes the cli is running on a x5460

the deamon is running on an i3 655

or something

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

this is not something that is awfull and bad

i see it as a poor user experience that probably could be fixed with some new upgrade.

ocb: just tested it with a timer, a sample transaction took ~1 second with my remote node

like afrter hit transfer addr amount,

so I'm a bit surprised that you regularly see 20 seconds :D

the user gets info like "gathering fee info"

Reticulating splines...

then "gathering decoys"

"Waiting for your incredibly slow disk (what is that, MFM ?)"

lol

what

Anyway, you might have missed "< moneromooo> Then try it on the daemon side."

And do check for I/O load on both.

(in addition to CPU load)

That's the "wa" column.

i will copy your commands and try it for next time.

OK

thanks so much

:)

How's everyone doing?

watching crd716 ask redundant questions....

cool

I *like* the XMR Art Fund! twitter.com/XMRArtFund/status/1474787942673489924