Skip to content

Conversation

@xiwenc
Copy link

@xiwenc xiwenc commented Sep 9, 2025

Change Overview

Kando consumes excessive memory when uploading large files to S3. See #3036

This PR changes the upload method to streaming. This is memory efficient.

Pull request type

Please check the type of change your PR introduces:

  • 🚧 Work in Progress
  • 🌈 Refactoring (no functional changes, no api changes)
  • 🐹 Trivial/Minor
  • 🐛 Bugfix
  • 🌻 Feature
  • 🗺️ Documentation
  • 🤖 Test
  • 🏗️ Build

Issues

Test Plan

Tested uploading a 2.7GB gz file and monitored the pod memory usage. It hovered around 600 MB.

  • 💪 Manual
  • ⚡ Unit test
  • 💚 E2E

In collaboration with Jouke Waleson <jouke@waleson.com>

Signed-off-by: Xiwen Cheng <x@cinaq.com>
@hairyhum
Copy link
Collaborator

Hi @xiwenc! Thanks for the contribution.
I don't think we currently have any e2e tests for blueprints using kando stream push command (most are using kando location push). Can you please provide a test (e.g. blueprint) we can run to verify the changes?

@hairyhum hairyhum requested a review from PrasadG193 September 29, 2025 17:51
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.

[BUG] Unexpected memory usage for kando

2 participants