Startups and small deployment - Best Practices for Deploying ClioSoft SOS on AWS

Startups and small deployment

A small startup might have only a few engineers working on an initial product idea. The notable characteristics of such organizations is that compute resources are scarce and often the CAD and IT teams are also part-time design engineers. The following figure shows a simple, on-premises deployment that might resemble a startup environment.

        This image shows an SOS7 startup environment.

SOS7 startup environment

The workflow of a startup environment typically includes:

  • The high-performance NAS file server exports volumes using NFS protocol

  • Each machine (servers and workstations) mounts the NAS-exported NFS volumes

  • Workstations render high-end graphics and the server accesses large data stored on the NFS volumes for typical activities

Design tools, such as layout editors, must be able to render complex graphics that display millions of polygons. The responsiveness of the EDA toolset directly affects user experience. Another challenge of this on-premises setup is that shared NFS/NAS drives can easily be a bottleneck. Local drives offer strong performance, but the complex logistics involved in replicating a large amount of ever-changing data on several local drives mean it’s not a practical solution for most customers.

SOS7 is optimized for this type of design environment, which includes shared, smart cache areas that hosts all the design files that are not being modified. User access to these design files is provided by tool-managed Linux symbolic links in the user’s working directory. This is one key feature used by most ClioSoft customers to create links to the cache workspace, because it can help to reduce the storage requirements of the design team by up to 90%.