Ram / Memory Consumption

[gregg-cbs]

My nodejs server is quite thirsty on ram.

We are looking into it. It seems arktype is shooting up the memory.

Has memory impact been analyzed for arktype and creating schemas?

[gregg-cbs]

Just by including arktype into our project without even using it, after building and tree shaking this is what happens to our memory.

Before including arktype (12mbs ram)

After including arktype (23mbs ram)

Memory goes from 12mbs to 23mbs. It seems the memory shoots even higher when starting to use arktype and creating schemas.

[ssalbdivad]

Generally the trade off with ArkType is that initialization/schema creation includes a lot of optimization work that is relatively expensive. Once you're validating, it's extremely cheap and has great built-in error messages.

If initialization speed a bottleneck for your overall performance, I would recommend lazily loading arktype if possible or using a validator like Valibot which has very cheap initialization at the cost of some validation speed + error message clarity.

This is certainly something I'm interested in looking into in optimizing further via precompilation and potentially eventually releasing something akin to @zod/mini that would be optimized for this scenario out of the box, but if the current trade offs are poorly suited to your needs I might go with another validator for now.

[gregg-cbs]

Thanks for the reply. It was a surprise to me because ark talks about being fast but does not talk about memory consumption.

We are doing a deep dive into our big memory consumers and will report any findings here if they are relevant to ark.

On our 512MB VM's ram is becoming an issue, our project is not overly complicated so it came as a surprise that our RAM was sitting at 400MBs. This could be due to other factors but arks memory consumption was a surprise however that might not be our main issue and we will probably find some other packages are not tree-shakeable or are simply large.