STRESS testing: submitting too many requests kills parity

[rstormsf]

thread '<unnamed>' panicked at 'failed to create an OS RNG: Error { repr: Os { code: 23, message: "Too many open files in system" } }', src/libcore/result.rs:859
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
   1: std::panicking::default_hook::{{closure}}
   2: std::panicking::default_hook
   3: std::panicking::rust_panic_with_hook
   4: std::panicking::begin_panic
   5: std::panicking::begin_panic_fmt
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::result::unwrap_failed
   9: std::collections::hash::map::RandomState::new::KEYS::__init
  10: regex::dfa::Cache::new
  11: <thread_local::CachedThreadLocal<T>>::get_or::{{closure}}
  12: <thread_local::CachedThreadLocal<T>>::get_or_try_slow
  13: regex::re_unicode::Regex::find_iter
  14: ethcore_logger::setup_log::{{closure}}
  15: <env_logger::Logger as log::Log>::log
  16: log::__log
  17: <rotor::creator::LoopInstance<M>>::run
  18: core::ptr::drop_in_place
  19: std::panicking::try::do_call

I simply throw a lot of transactions at the node

I'm running:
Parity//v1.7.0-beta-5f2cabd-20170727/x86_64-macos/rustc1.18.0

I can provide the script, once I get an approval

[5chdn]

too many open files is an OS error. https://superuser.com/questions/433746/is-there-a-fix-for-the-too-many-open-files-in-system-error-on-os-x-10-7-1

Should not panic though.

[arkpar]

A script would be useful indeed. How exactly do you connect to parity API? Could it be that you are creating a new connection for each request?

[5chdn]

Might be related: #6516

[5chdn]

Closing due to inactivity.