Structr Support - What are the hardware requirements of running Structr?

The Structr Knowledge Graph
- About Structr
  - Architecture
  - Typical Use Cases
  - Case Studies
    - Flexibel, schnell, einfach: MDM über…
    - Flexible, Fast, Easy: MDM Throughout…
- Getting Started
  - Installation and Setup
    - Remote Neo4j mode
    - Structr on GNU/Linux
    - Structr on Mac OS X
    - Structr on Windows
    - Backup an Existing Structr Installation
  - Anatomy of a Structr Application
  - Guides and Tutorials
    - Tips & Tricks
    - Tutorials
    - Videos
- Working with Structr
  - Administration
    - Command-Line Tools
    - Maintenance Commands
    - Start/Stop Scripts
    - Server Configuration
  - Concepts
    - Changelog
    - Flow Engine
    - Pages and Templates
    - Custom Types
    - Active Elements
    - Data Binding
    - Tooling for Interactive Apps (aka Edit…
    - Visibility
    - Resource Access Grants
    - Permission Resolution
    - Virtual Types
    - Initial Seed
    - User Self-Registration
    - Counters
  - User Interface
    - Dashboard
    - Graph
    - Pages
    - Filesystem
    - Security
    - Data
    - Schema Editor
  - StructrScript
    - Builtin Functions Availability Matrix
    - Keywords and Dot-Notation
    - Built-In Functions
    - Serverside JavaScript
  - Server APIs / Interfaces
    - HTTP Upload
    - LDAP / Active Directory
    - Messaging-Engine Module
    - REST
    - SSH
    - FTP
    - CMIS
    - XMPP
- FAQ
  - How can I fix…
  - How can I supply property values to a…
  - What are the hardware requirements of…
  - What is "passive indexing"?
  - What performance can I expect from…
  - java.lang.NoClassDefFoundError: Could…
- Advanced Topics
  - Create a File from a Base64-encoded…
  - Creating non-HTML output
  - Debugging Structr-UI
  - Deployment
  - Dynamic Forms
  - Fulltext indexing
    - Tesseract OCR
  - Graph-Browser
    - Graph-Browser Modules
  - Localization
  - Multi-Site Configuration
  - Periodic command scheduling
  - Store encrypted strings in the database
  - Translation
  - Web-Feed
  - CORS
- Resources
  - GitHub
  - Google Group / Mailing List
  - Hosting
  - Stackoverflow
  - neo4j.com
  - structr.com
  - structr.org
- Contribute
- Developer Resources

What are the hardware requirements of running Structr?

Structr runs fine on any device which is capable to run Java. However, due its anatomy and the nature of the embedded components like the Neo4j graph database and the Jetty HTTP server, the following minimum hardware requirements are given:

Absolute Minimum Hardware Specs

Architecture	ARM Cortex A8 SoC
RAM	512 MB
JVM Heap Space	not preallocated
CPU	Single Core 1 GHz
HDD	4 GB

(Tested on a $9 C.H.I.P. computer.) Please note that you can’t expect any decent performance on this type of hardware. Typical start-up time of Structr on this kind of hardware can be up to several minutes.

Typical Minimum Hardware

Architecture	x86_64
RAM	2 GB
JVM Heap Space	1 GB
CPU Speed	Dual Core 2 GHz
HDD	50 GB

Recommended Hardware

Architecture	x86_64
RAM	16 GB
JVM Heap Space	8 GB
CPU Speed	Quad Core 3 GHz
HDD	100 GB SSD

About this article

Last change	2019-03-11
Topics	Structr 2.0

Navigation