epam / epam/cloud-pipeline

Improve pipe fuse logging performance

Open
#856 0 comments 0 reactions 0 assignees View on GitHub
kind/enhancement priority/low sys/cli
Dominant language
Java
Stars
163
Forks
65
Avg merge
11h 46m
Merged PRs (30d)
29

Description

**Background**

It was seen that pipe fuse performance can be affected significantly by logging. Currently pipe fuse generates lots of logs and even though most of them are debug logs which are disabled by default they still has some impact.

In order to improve overall performance of the fuse which will be affected even more with the introduction of synchronization in #847 several approaches can be used.

**Approach**

First of all, amount of logs with the default logging level should be minimized. Moreover no string interpolation should be used within logging calls. There are other approaches to minimize logging impact such as completely disabled logging. They should be uncovered and tested too.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by locating the pipe fuse logging calls, measure their effect at the default logging level, and inspect how disabled logging is handled; done means reduced default logging overhead, no string interpolation in logging calls, and tested alternatives.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
infrastructure, performance
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.