$include_dir="/home/hyper-archives/boost-users/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [Boost-users] UDP Echo Server
From: Mark Hieber (hieberm_at_[hidden])
Date: 2017-08-25 01:07:49
Sorry, accidentally hit send.
I have a working version of a UDP Echo Server that listens to multiple
ports and echos responses back. This implementation uses threads (one per
port) and uses boost::asio and async reads and writes.
This implementation works fine with machines with multiple virtual cores,
but I also need to run this on a machine that has one virtual core
available. I will listen to about 10 ports at this time, but the number of
ports could grow.
My questions are:
1) Should I re-write this to run on one core? We see performance issues on
one core.
2) Is this a good candidate for boost::fibers? If so, what approach should
I take? Still use boost::asio and async reads and writes?
I am a bit confused on which way to go with this. I would appreciate some
helpful hints or guidance.
Thanks,
On Thu, Aug 24, 2017 at 6:01 PM, Mark Hieber <hieberm_at_[hidden]> wrote:
> Hi,
>
>
>