Hi,
this is the first time that it happens to me that I have a possible way
to improve libev. I thought that it was impossible but I think that I
got a good idea!
In ev_run(), there is this code:
/* from now on, we want a pipe-wake-up */
pipe_write_wanted = 1;
ECB_MEMORY
this is a trading bot interfacing with the exchange by using the
WebSockets protocol.
Under the hood, it is using libev.
It did make millions of $10 or less transactions during 15 days. It did
run flawlessly nonstop from March 7-15 24/24 7 days for a total of 68
millions USD trading volume!
I ha
On Fri, 2023-09-08 at 18:26 -0400, Olivier Langlois wrote:
> Any time ev_async_send() is called, there is no doubt that the
> watcher
> is active.
>
> The possible race condition is whether or not the async watcher will
> be
> in pending state when stopped.
>
> After
On Fri, 2023-09-08 at 21:39 +0200, Marc Lehmann wrote:
> On Fri, Sep 08, 2023 at 02:32:46PM -0400, Olivier Langlois
> wrote:
> > but beside that, I have a hard time figuring out what could cause a
> > segv into that small function...
>
> Almost always, this is caused by
On Sun, 2022-08-28 at 16:31 +0200, Marc Lehmann wrote:
> On Sat, Aug 27, 2022 at 09:09:10PM +0530, Mushtaq Khan
> wrote:
> > I see a segmentation fault ev_feed_event() called from
> > timer_reify(). I
> > used to see this issue intermittently now i see this quite
> > consistently in
> > my work en
Sorry for the silly question...
I usually find the answer to that type of questions by doing .configure
--help or reading a build.txt file or something like that.
I did not find the answer for libev...
thx!
Olivier
___
libev mailing list
libev@lists.sc
I wasn't aware of libeio. I will take a look into it...
Just to clarify my intent, the second patch wasn't meant for
submission. Of course, I know that this cannot be accepted. The purpose
for sharing it was to share what I was doing in terms of
experimentation with your lib.
On Thu, 2021-05-06 a
On Tue, 2021-05-04 at 12:57 +0200, Marc Lehmann wrote:
> Thanks for trying out the iouring backend.
>
> On Wed, Apr 28, 2021 at 11:24:49AM -0400, Olivier Langlois
> wrote:
> > I believe that in order to achieve the performance gain that io_uring
> > can deliver, you w
, Olivier Langlois wrote:
> Hi,
>
> I just wanted to report back that my usage with libev iouring backend
> appears to be working super fine.
>
> It is a WebSocket client opening about 64 TCP connections.
> The test has been performed with kernel 5.11.14.
>
> By switching fro
Hi,
I just wanted to report back that my usage with libev iouring backend
appears to be working super fine.
It is a WebSocket client opening about 64 TCP connections.
The test has been performed with kernel 5.11.14.
By switching from epoll backend to io_uring one, my process CPU usage
did drop f
I second that. I'm very interested in the current libev io_uring
support state.
I have seen a lot of commits for io_uring in the kernel 5.5.x releases
for fixing bugs.It must be much more stable than it was back in
December.
I have seen an article this morning touting io_uring performance in the
up
Hi,
I have just found out that creating a loop with:
ev_loop_new(EVBACKEND_LINUXAIO|EVFLAG_SIGNALFD)
resulted in having the signals not delivered.
BTW, what is libev current stand about AIO?
According to libev doc, it is the best backend on Linux.
However by reading libev release notes for v4.3
12 matches
Mail list logo
