Use num_cpus instead of hardcoding the number of threads for dns look_up.

In the next hyper_tls relase it should be possible to use the existing
cpu_pool executor.
This commit is contained in:
Jordan Petridis
2018-01-27 11:08:57 +02:00
parent 120d494280
commit d14973cf0d
4 changed files with 5 additions and 2 deletions
+1
View File
@@ -25,6 +25,7 @@ tokio-core = "0.1.12"
hyper-tls = "0.1.2"
native-tls = "0.1.5"
futures-cpupool = "0.1.8"
num_cpus = "1.8.0"
[dependencies.diesel]
features = ["sqlite", "r2d2"]
+1
View File
@@ -44,6 +44,7 @@ extern crate hyper;
extern crate hyper_tls;
extern crate itertools;
extern crate native_tls;
extern crate num_cpus;
extern crate rayon;
extern crate reqwest;
extern crate rfc822_sanitizer;
+2 -2
View File
@@ -10,6 +10,7 @@ use hyper::client::HttpConnector;
use hyper_tls::HttpsConnector;
use tokio_core::reactor::Core;
use num_cpus;
use rss;
use Source;
@@ -78,8 +79,7 @@ pub fn run(sources: Vec<Source>, ignore_etags: bool) -> Result<()> {
let mut core = Core::new()?;
let handle = core.handle();
let client = Client::configure()
// FIXME: numcpus instead of 4
.connector(HttpsConnector::new(4, &handle)?)
.connector(HttpsConnector::new(num_cpus::get(), &handle)?)
.build(&handle);
pipeline(sources, ignore_etags, &mut core, pool, client)