Re: [zeromq-dev] profiling a czmq program with gprof

2012-09-23 Thread Michael Haberler
Am 23.09.2012 um 01:59 schrieb Steven McCoy: On 22 September 2012 16:41, Michael Haberler mai...@mah.priv.at wrote: I tried to profile a program using czmq with gprof which runs fine when compiled with gcc, but without -pg with -pq, the program cops out with: 12-09-22 22:37:24 I:

Re: [zeromq-dev] High water mark notification for publisher

2012-09-23 Thread Paul Colomiets
Hi Edwin, On Sun, Sep 23, 2012 at 6:23 AM, Edwin Amsler edwinams...@thinkboxsoftware.com wrote: I have a mechanism out of band over TCP that re-requests pieces once the transfer is done, but I'm never actually sure when it's done sending so I just wait 1 minute before re-requesting. If I had

Re: [zeromq-dev] profiling a czmq program with gprof

2012-09-23 Thread Steven McCoy
On 23 September 2012 02:03, Michael Haberler mai...@mah.priv.at wrote: even then though, gprof output remains pretty useless. You can feed oprofile output through gprof then you do get something useful. -- Steve-o ___ zeromq-dev mailing list

Re: [zeromq-dev] Assertion failed: !(msg_-flags () msg_t::more)(session_base.cpp:157)

2012-09-23 Thread Ian Barber
On Fri, Sep 21, 2012 at 6:15 PM, RohanB roh...@cs.uchicago.edu wrote: Its going to be really hard to reproduce this one. It works perfectly on one box and not the other. Same build. Here's the difference though. The box on which it works is 64 bit SuSe. The one where it doesn't is a 32 bit

Re: [zeromq-dev] High water mark notification for publisher

2012-09-23 Thread Justin Karneges
I am also dealing with a file-sending case and want to avoid sending at read speed for the same reasons. I've decided to use the credits-based flow control approach Pieter suggested. For pub/sub, you really only need one subscriber sending credits, but the nice thing about the approach is that

Re: [zeromq-dev] High water mark notification for publisher

2012-09-23 Thread Edwin Amsler
Thanks for the ideas Paul. My out of band work is just to let late joiners and those clients whose disks couldn't write fast enough (they abandon messages destined for disk and mark that down). They notify the server of what parts they missed, and the server broadcasts again. It's a bit like

Re: [zeromq-dev] broken pipe on remote shutdown

2012-09-23 Thread Yi Ding
On Thu, Sep 20, 2012 at 4:38 AM, Pieter Hintjens p...@imatix.com wrote: On Wed, Sep 19, 2012 at 4:49 PM, Yi Ding yi.s.d...@gmail.com wrote: I got a strange error today where one of my servers threw an assertion when I killed a remote. Here's the error: Broken pipe