wordpress-mobile / wordpress-mobile/WordPress-Android
Don't flush the AppLogs on every write
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
In #11536 we are adding log encryption and as part of it, we are flushing the logs in each write so we don't miss the log when the app crashes. Although it's necessary at this point, we should look into different ways to handle this so we are not hogging the IO.
cc @jkmassel
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing #11536 and tracing the AppLogs write path to understand why each write currently flushes logs for encryption and crash safety. Compare possible approaches for reducing IO without losing required logs, then document or implement the selected approach and verify that encrypted logging still handles crashes correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100