The short version
Alpha 0.1.1 is much smaller to download and install on all three platforms. On macOS it also uses less RAM. On Windows and Ubuntu it is not more economical yet: with modules open and during SSH and SFTP work it uses considerably more RAM than Beta 0.1.0, and CPU use during that work is higher on every platform. We publish these numbers so you can decide with the facts, including the ones that do not favor the new version.
Measured values
Each cell shows Beta 0.1.0 → Alpha 0.1.1. Lower is better. Values are averages; the last row was measured only on 0.1.1, because the same test on 0.1.0 needs a native file dialog.
| Beta 0.1.0 ⟶ Alpha 0.1.1 | macOS | Windows | Ubuntu |
|---|---|---|---|
| InstallerSize of the downloaded package. | 160 ⟶ 21 MB | 114 ⟶ 12 MB | 114 ⟶ 20 MB |
| Installed applicationDisk space after installation. | 352 ⟶ 61 MiB | 422 ⟶ 53 MiB | 392 ⟶ 62 MiB |
| RAM after unlockingThe vault is unlocked and no module is open. | 482 ⟶ 315 MiB | 353 ⟶ 374 MiB | 727 ⟶ 680 MiB |
| RAM with 3 modulesSystem Monitor, File Manager and Log Viewer are open. | 861 ⟶ 496 MiB | 664 ⟶ 1238 MiB | 1102 ⟶ 1935 MiB |
| RAM during SSH and SFTPAdditionally a live terminal and reading over SFTP. | 878 ⟶ 523 MiB | 683 ⟶ 1292 MiB | 1146 ⟶ 2057 MiB |
| CPU during SSH and SFTPPercentage of one core. | 0.3 ⟶ 2.9 | 2.0 ⟶ 12.4 | 8.7 ⟶ 23.7 |
| CPU while downloading 512 MiB repeatedlyPercentage of one core; measured only on 0.1.1. | 17.9 | 3.6 | 23.9 |
How it was measured
Measured on 30 and 31 October 2026 in a single run, 40 seconds per phase after 12 seconds of settling, against the same test server. RAM is the sum of resident memory or working set across all application processes, so shared memory is counted more than once. CPU is a percentage of one core. Ubuntu ran under Xvfb without a GPU and Windows in a session with no logged-in user, which can affect WebView behavior. Alpha 0.1.1 was a release build with test automation enabled; Beta 0.1.0 was the official package. This is one measurement, not a general benchmark, and your values will differ. The very low 0.1.0 CPU value on macOS looks suspicious and has not been confirmed.
Why the numbers may look like this
The most likely explanation is that in 0.1.1 every module opens its own window with its own WebView processes, which adds up as more modules are open. This has not been proven yet. The measurement method also counts shared memory repeatedly, so it may overstate the difference for an application with many processes. We are not fixing this in the current alpha; the work is planned for later, without a promised date.
What this means for you
If you want a small download and work on macOS, 0.1.1 is already ahead in these measurements. If you have little memory on Windows or Ubuntu and keep several modules open, Beta 0.1.0 currently uses less RAM. Alpha 0.1.1 has also had less testing overall, so back up your data before trying it.