How can I implement a blocking queue mechanism with futures::sync::mpsc::channel?
I am trying to understand how futures::sync::mpsc::Receiver works. In the below example, the receiver thread sleeps for two seconds and the sender sends every second.
I expect that the sender will need to be blocked because of the wait and then send when the buffer is released.
What I see instead is that it is deadlocked after a time. Increasing the buffer of the channel only extends the time until it is blocked.
What should I do to make the sender send data when the buffer is available and put some backpressure to the sender in such cases? futures::sync::mpsc::channel has its own documentation, but I do not understand how to use it properly.
extern crate futures;
extern crate tokio_core;
use std::thread, time;
use futures::sync::mpsc;
use futures::Future, Sink, Stream;
use tokio_core::reactor::Core;
#[derive(Debug)]
struct Stats
pub success: usize,
pub failure: usize,
fn main()
let mut core = Core::new().expect("Failed to create core");
let remote = core.remote();
let (tx, rx) = mpsc::channel(1);
thread::spawn(move
rust future rust-tokio
add a comment |
I am trying to understand how futures::sync::mpsc::Receiver works. In the below example, the receiver thread sleeps for two seconds and the sender sends every second.
I expect that the sender will need to be blocked because of the wait and then send when the buffer is released.
What I see instead is that it is deadlocked after a time. Increasing the buffer of the channel only extends the time until it is blocked.
What should I do to make the sender send data when the buffer is available and put some backpressure to the sender in such cases? futures::sync::mpsc::channel has its own documentation, but I do not understand how to use it properly.
extern crate futures;
extern crate tokio_core;
use std::thread, time;
use futures::sync::mpsc;
use futures::Future, Sink, Stream;
use tokio_core::reactor::Core;
#[derive(Debug)]
struct Stats
pub success: usize,
pub failure: usize,
fn main()
let mut core = Core::new().expect("Failed to create core");
let remote = core.remote();
let (tx, rx) = mpsc::channel(1);
thread::spawn(move
rust future rust-tokio
Where doesfutures::donecome from? It's not a part of the current version of the futures crate.
– Shepmaster
Nov 13 at 3:05
add a comment |
I am trying to understand how futures::sync::mpsc::Receiver works. In the below example, the receiver thread sleeps for two seconds and the sender sends every second.
I expect that the sender will need to be blocked because of the wait and then send when the buffer is released.
What I see instead is that it is deadlocked after a time. Increasing the buffer of the channel only extends the time until it is blocked.
What should I do to make the sender send data when the buffer is available and put some backpressure to the sender in such cases? futures::sync::mpsc::channel has its own documentation, but I do not understand how to use it properly.
extern crate futures;
extern crate tokio_core;
use std::thread, time;
use futures::sync::mpsc;
use futures::Future, Sink, Stream;
use tokio_core::reactor::Core;
#[derive(Debug)]
struct Stats
pub success: usize,
pub failure: usize,
fn main()
let mut core = Core::new().expect("Failed to create core");
let remote = core.remote();
let (tx, rx) = mpsc::channel(1);
thread::spawn(move
rust future rust-tokio
I am trying to understand how futures::sync::mpsc::Receiver works. In the below example, the receiver thread sleeps for two seconds and the sender sends every second.
I expect that the sender will need to be blocked because of the wait and then send when the buffer is released.
What I see instead is that it is deadlocked after a time. Increasing the buffer of the channel only extends the time until it is blocked.
What should I do to make the sender send data when the buffer is available and put some backpressure to the sender in such cases? futures::sync::mpsc::channel has its own documentation, but I do not understand how to use it properly.
extern crate futures;
extern crate tokio_core;
use std::thread, time;
use futures::sync::mpsc;
use futures::Future, Sink, Stream;
use tokio_core::reactor::Core;
#[derive(Debug)]
struct Stats
pub success: usize,
pub failure: usize,
fn main()
let mut core = Core::new().expect("Failed to create core");
let remote = core.remote();
let (tx, rx) = mpsc::channel(1);
thread::spawn(move
rust future rust-tokio
rust future rust-tokio
edited Nov 13 at 3:04
Shepmaster
147k12282416
147k12282416
asked Nov 12 at 14:11
Akiner Alkan
560215
560215
Where doesfutures::donecome from? It's not a part of the current version of the futures crate.
– Shepmaster
Nov 13 at 3:05
add a comment |
Where doesfutures::donecome from? It's not a part of the current version of the futures crate.
– Shepmaster
Nov 13 at 3:05
Where does
futures::done come from? It's not a part of the current version of the futures crate.– Shepmaster
Nov 13 at 3:05
Where does
futures::done come from? It's not a part of the current version of the futures crate.– Shepmaster
Nov 13 at 3:05
add a comment |
1 Answer
1
active
oldest
votes
Never call
waitinside of a future. That's blocking, and blocking should never be done inside a future.Never call
sleepinside of a future. That's blocking, and blocking should never be done inside a future.Channel backpressure is implemented by the fact that
sendconsumes theSenderand returns a future. The future yields theSenderback to you when there is room in the queue.
extern crate futures; // 0.1.25
extern crate tokio; // 0.1.11
use futures::future, sync::mpsc, Future, Sink, Stream;
use std::time::Duration;
use tokio::timer::Interval;
#[derive(Debug)]
struct Stats
pub success: usize,
pub failure: usize,
fn main()
tokio::run(future::lazy(
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53263942%2fhow-can-i-implement-a-blocking-queue-mechanism-with-futuressyncmpscchannel%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Never call
waitinside of a future. That's blocking, and blocking should never be done inside a future.Never call
sleepinside of a future. That's blocking, and blocking should never be done inside a future.Channel backpressure is implemented by the fact that
sendconsumes theSenderand returns a future. The future yields theSenderback to you when there is room in the queue.
extern crate futures; // 0.1.25
extern crate tokio; // 0.1.11
use futures::future, sync::mpsc, Future, Sink, Stream;
use std::time::Duration;
use tokio::timer::Interval;
#[derive(Debug)]
struct Stats
pub success: usize,
pub failure: usize,
fn main()
tokio::run(future::lazy(
add a comment |
Never call
waitinside of a future. That's blocking, and blocking should never be done inside a future.Never call
sleepinside of a future. That's blocking, and blocking should never be done inside a future.Channel backpressure is implemented by the fact that
sendconsumes theSenderand returns a future. The future yields theSenderback to you when there is room in the queue.
extern crate futures; // 0.1.25
extern crate tokio; // 0.1.11
use futures::future, sync::mpsc, Future, Sink, Stream;
use std::time::Duration;
use tokio::timer::Interval;
#[derive(Debug)]
struct Stats
pub success: usize,
pub failure: usize,
fn main()
tokio::run(future::lazy(
add a comment |
Never call
waitinside of a future. That's blocking, and blocking should never be done inside a future.Never call
sleepinside of a future. That's blocking, and blocking should never be done inside a future.Channel backpressure is implemented by the fact that
sendconsumes theSenderand returns a future. The future yields theSenderback to you when there is room in the queue.
extern crate futures; // 0.1.25
extern crate tokio; // 0.1.11
use futures::future, sync::mpsc, Future, Sink, Stream;
use std::time::Duration;
use tokio::timer::Interval;
#[derive(Debug)]
struct Stats
pub success: usize,
pub failure: usize,
fn main()
tokio::run(future::lazy(
Never call
waitinside of a future. That's blocking, and blocking should never be done inside a future.Never call
sleepinside of a future. That's blocking, and blocking should never be done inside a future.Channel backpressure is implemented by the fact that
sendconsumes theSenderand returns a future. The future yields theSenderback to you when there is room in the queue.
extern crate futures; // 0.1.25
extern crate tokio; // 0.1.11
use futures::future, sync::mpsc, Future, Sink, Stream;
use std::time::Duration;
use tokio::timer::Interval;
#[derive(Debug)]
struct Stats
pub success: usize,
pub failure: usize,
fn main()
tokio::run(future::lazy(
answered Nov 13 at 3:30
Shepmaster
147k12282416
147k12282416
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53263942%2fhow-can-i-implement-a-blocking-queue-mechanism-with-futuressyncmpscchannel%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Where does
futures::donecome from? It's not a part of the current version of the futures crate.– Shepmaster
Nov 13 at 3:05