Status 413 Payload Too Large

[jamesbeadle]

Hi,

I get the error " Failed during wasm installation call: The replica returned an HTTP Error: Http Error: status 413 Payload Too Large" when deploying locally.

Any help appreciated.

[Gekctek]

Looks like the canister WASM is too large. You can make it smaller if you have use optimizers for compiling, but only so much.
I ran into this because i had a few actor class references, which bloats the canister WASM

[Gekctek]

I also heard you can zip it, but i haven’t done that

[jamesbeadle]

Yeah the problem has occurred ever since adding actor class references that are used in the multi-canister architecture.

Are there any docs on using optimisers? I’m close to the limit and shouldn’t need any more actor classes just yet…

I’ve also seen some stuff on using gzip but again just looking for a pointer in the right direction on how to do it.

[Gekctek]

8: Optimizing canisters | Internet Computer

Large web assembly modules | Internet Computer

Motoko actor class deployment options

I have an issue where I have a few actor classes that I want to deploy from my main canister but I am running into an issue where each actor class takes about ~500KB of WASM space, so im looking into alternative options. Here is what I see as options Spread out the actor classes to other canister(s) Deploy actor classes from dfx (This might have an issue of not being deployable via a DAO) ? Any help or suggestions would be appreciated

[jamesbeadle]

Exactly what I was looking for, thanks.