3 ms·
Not sure. To me, they seem to nail all three of them. - The desktop application I build end up being 16M which seems small enough to me. - The performance is
by capableweb 4y ago
Not sure. To me, they seem to nail all three of them.
- The desktop application I build end up being 16M which seems small enough to me.
- The performance is generally good enough, even though I haven't spent any time optimizing things (here is loading 1000 comments from a HN thread https://ditzes.com/item/31742590 https://ditzes.com/item/31742590, even faster if you use the local version [obviously])
- stjohnswarts 4y agoSure but when it's loaded how much memory does it use?
- capableweb 4y agoJust as a reference, the application I'm building features a lot things inside the final binary, that might affect ram usage, so this is not a "hello-world" example but a real application, with a SPA built-into the binary and loaded into RAM, together with a HTTP API and more (fuller list here: https://news.ycombinator.com/item?id=31765186 https://news.ycombinator.com/item?id=31765186). With that said, `ps_mem` (https://github.com/pixelb/ps_mem https://github.com/pixelb/ps_mem) reports that the memory usage is 58.7 MiB after starting the Tauri application. If I run just the HTTP API, memory usage ends up being 19.4 MiB. So I guess in that sense, the overhead of Tauri is about ~39.3 MiB. For my use case, that's pretty acceptable. Edit: full data in case it interests people: Desktop application: Private + Shared = RAM used Program 47.0 MiB + 11.7 MiB = 58.7 MiB ditzes Just the API: Private + Shared = RAM used Program 19.0 MiB + 345.5 KiB = 19.4 MiB api