From 33fbdafac10d9289cbc0bb0b351eb0feabfae36a Mon Sep 17 00:00:00 2001 From: baoachun <962571062@qq.com> Date: Sat, 25 Sep 2021 10:23:11 +0800 Subject: [PATCH] temporarily fix the performance drop of recurrent op (#36053) --- paddle/fluid/operators/recurrent_op.cc | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/paddle/fluid/operators/recurrent_op.cc b/paddle/fluid/operators/recurrent_op.cc index 92e5e4a0cd..556f1bccd1 100644 --- a/paddle/fluid/operators/recurrent_op.cc +++ b/paddle/fluid/operators/recurrent_op.cc @@ -215,13 +215,7 @@ void RecurrentOp::RunImpl(const framework::Scope &scope, kSkipEagerDeletionVars), /*skip_ref_cnt_vars*/ true); - static std::mutex mutex; - std::lock_guard lock(mutex); StepScopes scopes = CreateStepScopes(dev_ctx, scope, seq_len); - // TODO(gfwm2013) Function CreateStepScopes would make segmentation fault in - // multithreading in eval process, so we use a mutex before function - // CreateStepScopes to make sure that the computing process is correct. This - // problem will fix in next pull request. for (size_t i = 0; i < seq_len; ++i) { size_t seq_offset = reverse ? seq_len - i - 1 : i; VLOG(3) << "Recurrent operate at the time step " << seq_offset; @@ -292,6 +286,11 @@ void RecurrentOp::RunImpl(const framework::Scope &scope, StepScopes RecurrentOp::CreateStepScopes(const platform::DeviceContext &dev_ctx, const framework::Scope &scope, size_t seq_len) const { + static std::mutex mutex; + std::lock_guard lock(mutex); + // TODO(baoachun) Function CreateStepScopes may lead to segmentation + // fault in multithreading in eval process. The performance drop of + // adding mutex need to be fixed. auto *var = scope.FindVar(Output(kStepScopes)); PADDLE_ENFORCE_NOT_NULL(var, platform::errors::InvalidArgument( "RecurrentOp gets empty StepScopes var")); -- GitLab