Skip to content

Conversation

@found-cake
Copy link
Owner

  • use persistent and temporary data storage(double storage)
  • transaction
  • remove batch methods

@found-cake found-cake changed the title Double Data Storage #6 Double Data Storage Aug 16, 2025
@found-cake
Copy link
Owner Author

After reviewing the benchmark results, I'm closing this PR due to significant performance regressions:

Performance Issues:

  • Memory usage increased by 170%
  • Basic Get operation performance degraded by 23%

Root Cause:
The dual storage architecture introduces unavoidable overhead from dual locking mechanisms and data duplication, which conflicts with the core principles of cache systems that prioritize speed and efficiency.

Next Steps:
I will implement the transaction functionality using the existing single database approach instead, which should maintain performance while providing the necessary transactional capabilities.

@found-cake found-cake closed this Aug 17, 2025
@found-cake found-cake deleted the feature/split-cache branch August 17, 2025 05:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant