CHILI Publisher – Systems Specifications

<back to product page

Minimum System requirements 

OS: Windows 2008 R2 web edition (English version is strongly recommended)

Memory: 4Gb RAM

CPU: 4 cores (2 cpu x 2 cores), 2.2Ghz

HD: All HD-types will do, but SATA is minimum

Connection to the Internet must be enabled

When more than one network card is installed, make sure there is no confusion with default gateways

These are MINIMUM requirements. For use in production environments with large amounts of concurrent users, high throughput of files and/or severe SLA requirements, please consider the recommended requirements as minimal.

Disk setup

See windows documentation for requirements, depending on the version of the OS

Application: Minimum 1GB, 5GB Recommended

Data: Totally up to your needs

10 documents with 10 images each (10MB) = 10 x 10 x 10 = 1GB

Keep in mind that CHILI Publisher is a graphical application, which will store a potentially large amount of images. While we can optimize those in some cases, you may reduce this by informing your designers not to use unnecessarily bloated image formats for the online environment (eg: 500Mb tiff files which will only be used on a small output size).

Also keep in mind that the CHILI Publisher application makes the assumption that performance is more important to its customers than low disk usage. Many files are cached on disk (including small size previews, but also potentially larger sized production versions of an image). This greatly increases overall performance (graphical rendering only needs to happen once). The underlying philosophy is that it will cost our

customers less to add disk capacity than adding another server (and CHILI license).

Recommended 

System: Windows 2008 R2 web edition

Memory: 8Gb or higher

CPU: 16Cores (4 cpu x 4 cores or 16CPU x 1 core), >3Ghz

HD: SAS 15000 RPM or Solid State

When writing more files, see for RAID stategy for faster writing speeds

Network

Network components when hosting a CHILI Publisher application

– Webserver

– Application server

The webserver should be accessible for the end-users you would allow. The uplink from you webserver to the end-user should be a high speed uplink.

In house hosting has the advantage the connection to the local data is very fast (local network) but most upload capacities have no burst capacity. Concider hosting your application in a datacenter. While you might only use an average of 1Mbit, you can peak to 100Mbit in most datacenters.

This will be a big advantage in moments of high traffic.

 

When the CHILI Publish service is hosted on a different computer, the netwerk between the Webserver and Application server should be separated from the rest of the network.

Preferably you could make an seperate network (or through dedicated ports on the switch) between these two servers.

NOTE: any URL used to access CHILI Publisher (either directly or embedded within a portal) should also be accessible from the server itself. Some of our components connect to other components (the webservices) through the used URL. This might not show up immediately, but make a habit of either configuring DNS correctly for this, or to add the host name in the server’s hosts file.