On Wed, Nov 20, 2019 at 5:09 AM Robert Engels <reng...@ix.netcom.com> wrote:
>
> You should include -r to show the relative time stamps. This would be helpful.
Also tell us what the different processes are. I'm guessing that in
the fragment above 20441 is wine itself? What is file descriptor 7?
Perhaps you could put the whole trace online somewhere so that we can see it.
Ian
> On Nov 20, 2019, at 1:58 AM, miha.vrhov...@gmail.com wrote:
>
>
> The first wait is on read, the 2nd on futex
> [pid 20441] read(5,
> "\0\0\0@\0\0\0\0\20\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) =
> 64
> [pid 20441] rt_sigprocmask(SIG_SETMASK, [HUP INT USR1 USR2 ALRM CHLD IO],
> NULL, 8) = 0
> [pid 20441] rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM CHLD IO], [HUP
> INT USR1 USR2 ALRM CHLD IO], 8) = 0
> [pid 20441] rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM CHLD IO], [HUP
> INT USR1 USR2 ALRM CHLD IO], 8) = 0
> [pid 20441] writev(3,
> [{iov_base="\34\0\0\0000\0\0\0\0\0\0\0\2\0\0\0\250r\204\377\0\0\0\0\0ty\270\377\377\377\377"...,
> iov_len=64},
> {iov_base="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> iov_len=40}, {iov_base="\1\0\0\0\20\0\0\0", iov_len=8}], 3) = 112
> [pid 20441] read(5,
> "\3\1\0\0\0\0\0\0\330\2656\374w\237\325\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 64) = 64
> [pid 20441] rt_sigprocmask(SIG_SETMASK, [HUP INT USR1 USR2 ALRM CHLD IO],
> NULL, 8) = 0
> [pid 20441] rt_sigprocmask(SIG_SETMASK, [HUP INT USR1 USR2 ALRM CHLD IO],
> NULL, 8) = 0
> [pid 20441] read(7,
>
>
> <unfinished ...>
> [pid 20437] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
> [pid 20437] nanosleep({tv_sec=0, tv_nsec=20000}, NULL) = 0
> [pid 20437] futex(0x59fb70, FUTEX_WAIT_PRIVATE, 0, {tv_sec=60, tv_nsec=0}
>
>
> BR,
> Miha
>
> On Tuesday, November 19, 2019 at 10:09:12 PM UTC+1, Ian Lance Taylor wrote:
>>
>> On Tue, Nov 19, 2019 at 11:45 AM <miha.v...@gmail.com> wrote:
>> >
>> > > Doesn't seem to happen with a exec of "/usr/bin/date" so it is most
>> > > likely something wine+Go specific.
>> > Yeah, I did try catting the file and it was fast enough. So you are
>> > probably right.
>> >
>> > Whats interesting is if I do it indirectly via shell script (then this is
>> > only 5 times slower not 28): But still too slow. Hell PHP can't be faster
>> > at this than Go.
>>
>> Use strace -f to see what the Go program is doing.
>>
>> Ian
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/c12d38c3-618f-499a-bcaf-d2862272cfed%40googlegroups.com.
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/9553B4A3-0589-4D3B-A330-7AE867E2A3C5%40ix.netcom.com.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/CAOyqgcVvq_gZiB1hgbEsKw1Z_MW3y3OvHBb46fUNvaaE7vOXWw%40mail.gmail.com.
