What is the potential issue of a smaller LMDB?

[azilber]

Compiling on a 32bit ARM platform yields:

`error: literal out of range for usize
--> store/src/lmdb.rs:76:16
|
76 | .set_mapsize(549_755_813_888)
| ^^^^^^^^^^^^^^^
|
= note: #[deny(overflowing_literals)] on by default

error: aborting due to previous error

error: Could not compile grin_store.
`

I know 32bit is not supported... BUT, if lower env_builder.set_mapsize to 4_294_967_000 I can get it to build. What (and when) is the potential fubar moment expected? 😀

[ignopeverell]

A larger size is mostly future proofing. On 32 bits you limit your state storage to 2^32 bytes, which isn't that large for storage. That being said we're still very far from that, so you can start that way and monitor the size regularly.

[sesam]

can we have grin autodetect or keep a smaller value for limited archs? Maybe a build time flag or crate feature to get default grin building on more systems. And add to the build/contrib guide whats needed for some archs.

[0xmichalis]

can we have grin autodetect or keep a smaller value for limited archs? Maybe a build time flag or crate feature to get default grin building on more systems. And add to the build/contrib guide whats needed for some archs.

See also #1681

[yeastplume]

Think this is answered