-
Notifications
You must be signed in to change notification settings - Fork 653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEAT-#4524: Split Modin API and Memory log files #4526
Conversation
Signed-off-by: Naren Krishna <naren@ponder.io>
Signed-off-by: Naren Krishna <naren@ponder.io>
Codecov Report
@@ Coverage Diff @@
## master #4526 +/- ##
==========================================
+ Coverage 86.36% 88.57% +2.21%
==========================================
Files 228 229 +1
Lines 18413 18913 +500
==========================================
+ Hits 15902 16753 +851
+ Misses 2511 2160 -351
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
Signed-off-by: Naren Krishna <naren@ponder.io>
Signed-off-by: Naren Krishna <naren@ponder.io>
Signed-off-by: Naren Krishna <naren@ponder.io>
Signed-off-by: Naren Krishna <naren@ponder.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you @naren-ponder
Co-authored-by: Yaroslav Igoshev <Poolliver868@mail.ru>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me - left some minor comments. Couple of overall comments -
- I believe you need to use `` when writing in-line code in
.rst
files rather than just ` by itself. (e.g. ``code formatted text``) - The tense of the docs change from referring to a user and telling them what to expect to speaking in first person - would be good to unify that
- I noticed that the file size for both traces and memory logs are the same - is that by design, or have we considered allowing different file sizes for each? I imagine it could be possible for a user to want more of one than the other e.g., but this may also be over engineering.
The memory and API log sizes being the same is mostly a coincidence (was not designed that way), but I think making that configurable is not worth it. |
Signed-off-by: Naren Krishna <naren@ponder.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a quick comment. There's a shift in the docs from passive voice in the intro to active voice in the usage guide, but idk if thats too nitpicky
Usage example | ||
------------- | ||
**Developer Warning:** In some cases, running services like JupyterLab in the ``modin/modin`` directory may result in circular dependency issues. | ||
This is as a result of a name conflict between the ``modin/logging`` directory and the Python ``logging`` module, which may be used as a default in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is as a result of a name conflict between the ``modin/logging`` directory and the Python ``logging`` module, which may be used as a default in | |
This is due to a naming conflict between the ``modin/logging`` directory and the Python ``logging`` module, which may be used as a default in |
Signed-off-by: Naren Krishna <naren@ponder.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we mention that we only allow 10 additional files before we start roll-over - and also mention that the maximum memory logging can take is actually 10*LogMemorySize?
Signed-off-by: Naren Krishna <naren@ponder.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Signed-off-by: Naren Krishna naren@ponder.io
What do these changes do?
In the current approach to Modin logging, all the logs are logged to a single file. In this updated approach, we separate out the memory logs from the Modin API logs.
flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
git commit -s
docs/development/architecture.rst
is up-to-date