You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@teaclave.apache.org by GitBox <gi...@apache.org> on 2021/07/30 14:51:27 UTC

[GitHub] [incubator-teaclave] ya0guang commented on issue #533: The payload is too large, how to fix?

ya0guang commented on issue #533:
URL: https://github.com/apache/incubator-teaclave/issues/533#issuecomment-889945307


   Hi @xglreal this problem really exists and we're actively working on a fix.
   
   > How to fix this problem?
   
   Unfortunately, there is no sysctematical fix to this problem. We'll explore if there is a hot/quick fix to just enlarge the memory space so it can hold larger function input.
   
   > Or what the max size of payload file?
   
   Around 700KB.
   
   > Or how to increase the size of wasm that the enclave can accept?
   
   The problem originates in Teaclave's design. In current design, payloads are transmitted in *string*, which is bad for performance. We need to modify the APIs of Teaclave and it's internal protocol to support large function payload.
   
   If you want to try to reduce the size of wasm file, you may try [wasm-gc](https://crates.io/crates/wasm-gc/0.1.6) and add this snippet in `Cargo.toml`:
   
   ```
   [profile.release]
   lto = true
   opt-level = "s"
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@teaclave.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@teaclave.apache.org
For additional commands, e-mail: notifications-help@teaclave.apache.org