Reference
System Requirements
The browsers Holarch runs in, how much computer memory (RAM) a project of each size and language needs, and how long large projects take to open.
On this page
Holarch runs in your web browser. The project you open is held in the browser's memory while you work, so the memory your computer needs grows with the size of the project. This page lists the browsers and the memory (RAM) to plan for each project size.
Concepts
- Item: one element of the model, as counted on Home under Save status (for example "48,000 items"). See Plans and limits for what counts as an item.
- Memory (RAM): the working memory of your computer. It is not the disk space. On a Mac, see Apple menu → About This Mac. On Windows, see Settings → System → About.
- Language: each project is either LML or SysML v2. SysML v2 projects also run the SysML checker in the browser, so the table lists each language.
How to use it
When and why
Check this page before you work with a large project, or when you choose a computer for a team that will. A computer with too little memory still opens small projects. With a large project it slows down, or the browser reloads the tab to free memory.
Check what your computer needs
- Open the project and read the item count on Home under Save status.
Without access yet, use the size you expect the model to reach.
- Find the row for that size and the project's language in Memory by project size.
- Compare the recommended memory with your computer's memory.
If your computer has less, see Work with less memory.
Worked example: a team's 230,000-item model
A team plans a model of about 230,000 items in SysML v2. The row "Up to 250,000 items" recommends 9 GB. Two engineers have laptops with 8 GB. The team has two options:
- Give those two engineers computers with more memory.
- Split the model into two projects of about 115,000 items, one per subsystem, and connect them with cross-project links. A project of that size needs 7 GB.
A small project, such as the CubeSat EO-1 demo, runs on any computer that meets the browser requirements.
Work with less memory
- Close other tabs and programs before you open a large project. Each open tab holds its own copy of its project.
- Open one large project at a time. Close a project (Manage Projects) before you open the next one.
- Split a large model into several projects, for example one per subsystem or program. Use cross-project links to connect them.
- Reload the page after a long session with a very large project. Holarch keeps your changes; the save status shows Saved before you reload.
Tips and good practice
- Plan for the size the project will reach, not the size it starts at.
- Keep long reports and exports for a computer with memory to spare. A document or export of a whole large model needs memory on top of the open project.
Browsers
Use a current version of one of these browsers:
- Safari on macOS. Holarch is tested in Safari, and the figures on this page were measured in Safari.
- Chrome, Edge, or another Chromium-based browser, such as Brave or Opera.
- Firefox.
Chromium-based browsers and Firefox are tested less than Safari. Their memory use differs from Safari's, so leave the same headroom. Keep the browser up to date: Holarch uses current web features, such as WebAssembly.
Holarch is designed for a computer screen. It opens on phones and small tablets, for example to read a project, but modeling needs a computer. On a phone-size touch screen a slim notice above the top bar says so; Dismiss hides it in that browser.
When a browser lacks something Holarch needs to start, open or save projects, Holarch does not start. A page says This browser can't run Holarch and links to Safari, Chrome, Edge and Firefox; open Holarch in a current version of one of them.
When a browser lacks something only some features need, Holarch starts and works as usual, and those features say why they are unavailable when you open them. A notice above the top bar lists them; Dismiss hides it.
| Feature | Needs | Notes |
|---|---|---|
| Simulator | Background workers | |
| Importing zipped files (Word, Excel, ReqIF archives, zip packages), AI reading Word files, large imports in the hosted app | Compression streams | Safari 16.4, Chrome 103 and Firefox 113 and later have them. |
| Fill Down in the Database | Structured cloning | |
| SysML v2 projects (opening, creating, demos, tutorials, imports, copies) | WebAssembly and background workers | WebAssembly is often turned off by Lockdown Mode on Apple devices or by a browser policy. Allow it for the site, or use another browser. LML projects work without it. |
A browser version that is clearly out of date still opens Holarch, with a notice to update it.
Memory by project size
The recommended memory leaves room for the operating system, the browser and a few other programs next to Holarch. It applies equally to the hosted service and to Holarch installed on your own computer: the project always runs in the browser.
Size limits:
- Desktop app (Holarch installed on your computer): tested to 250,000 items per project, in LML and SysML v2.
- Hosted service (app.holarch.app): up to 50,000 items per project; link projects for larger programs with cross-project links, the Program Map and libraries.
- SysML v2 projects: 50,000 items is about 90,000 lines of SysML v2 text (roughly 8,000–10,000 definitions). Definitions, usages, packages and comments count; connections, flows, imports, other relationships and library elements do not. See Plans and limits.
The rows above 50,000 items apply to the desktop app.
| Project size | LML: recommended memory | SysML v2: recommended memory |
|---|---|---|
| Up to 50,000 items | 6 GB | 6 GB |
| Up to 100,000 items | 6 GB | 7 GB |
| Up to 150,000 items | 6 GB | 7 GB |
| Up to 200,000 items | 6 GB | 8 GB |
| Up to 250,000 items | 7 GB | 9 GB |
- How memory grows: the Holarch page itself uses about 100 MB with no project open. While a project opens, the tab needs about 40–60 MB more per 10,000 items for LML and about 100–155 MB per 10,000 items for SysML v2. While the project stays open, the tab keeps about half of that.
- Largest size tested: 250,000 items in the desktop app, in both languages.
- Editing adds little: after 100 edits, an LML project's tab used no more memory than before them. While the edits are saved, it can briefly need up to about 0.6 GB more; the recommended memory includes this.
What to expect
Large projects take a few seconds to open. A progress bar at the bottom of the window shows the steps. Measured in Safari against a test server, from the click until the page is ready to use; a SysML v2 project then runs its first model check in the background, with the progress bar, while you work. The rows above 50,000 items apply to the desktop app, which opens projects at least as fast; the hosted service holds up to 50,000 items per project:
| Project size | LML | SysML v2: page ready | SysML v2: first model check done |
|---|---|---|---|
| 50,000 items | about 1 s | about 2 s | about 4 s |
| 100,000 items | about 2 s | about 3 s | about 7 s |
| 150,000 items | about 3 s | about 4 s | about 12 s |
| 200,000 items | about 3 s | about 7 s | about 16 s |
| 250,000 items | about 4 s | about 8 s | about 19 s |
- A slow network connection adds the time to download the project. Holarch installed on your computer opens projects faster.
- The first visit to a page that reads the whole model, such as a matrix or a report, can take a few seconds.
Limits
- Hosted service (app.holarch.app): the item limit of your plan applies, up to 50,000 items per project (Team); link projects for larger programs. Desktop app (Holarch installed on your computer): tested to 250,000 items per project. See Plans and limits.
- The figures were measured in Safari on a Mac, and on a test server with the hosted service's settings. A slower computer takes longer to open a project; it needs about the same memory.
- Projects with many diagrams, long rich-text descriptions or many attachments open more slowly and need more memory than the generated test projects behind these figures.