This article describes the performance and content storage options for SOCKETWorx (SWx).  As concurrent usage increases, both processor, memory, and storage demand increases.

There are no performance settings within the SWx setup. Webpage load times are predominately governed by:
1) the page content being loaded
2) internet connectivity speeds
3) intranet connectivity speeds
4) involved application and data servers
The scope of this article only addresses the SWx; Azure Server performance tier levels.

SWx reads and writes to connected SQL servers.  It also reads and writes with connected Windows file storage directories.  All those transactions tax CPU and memory, so just like any PC, the more memory and computing power the faster the system is. There are 3 standard performance and storage tiers available.

0<10102 GB2 GB
1<502020 GB10 GB
2<2005040 GB20 GB
3>20010060 GB50 GB

Storage Options

Location 1: SQL / SQL Express

SWx connects to SQL Server directly using SQL Authenticated Logins.  SWx communicates with databases using read/write permissions. SQL Server Name and Login credentials are set to make SWx Connections and users interact to view, add, edit, and report on data Tables and Views.  

Self-hosted deployments; SQL Servers are hosted and managed by the users behind their firewalls.  Deploying SOCKETWorx and SQL instances on separate Windows servers adds a security level, where data stores are separate from application stores. 

SaaS Deployments: If SQL Server is deployed, it will reside behind SWx Webserver firewalls.   

Location 2: LAN/WAN Storage

SOCKETWorx provides the ability to view and markup various project documents (PDF's, Excel, Word, Image, and Text Documents) on a  per "Connection" basis.  These documents are stored in LAN/WAN Windows file directories on the same network as IIS Webservers hosting SOCKETWorx.  The IIS credentials for SOCKETWorx require access to these LAN/WAN locations too.  This way it can display, add, delete, and version documents.  Under self-hosted deployments, LAN/WAN directories and data stored are hosted by the client.  SOCKETWorx uses Roles and Permissions to provide user access to the various documents.  These roles and permissions are stored in SOCKETWorx Azure under client-specific site databases. 

Location 3: Amazon S3 Simple Cloud Storage

Numerous built-in services require connections with Amazon S3 storage.  These connections are commonly referred to as S3 buckets. SOCKETWorx should only be set up using non-public/Private Buckets. File versions and revisions are stored in these buckets for retrieval on demand.

SOCKETWorx subscribers can use their own S3 setup and security on demand, otherwise, these storage services will be provided under performance tiers.  NOTE; Self-hosted storage is included within Tiers whether consumed or not.

In a company-specific SaaS environment, Amazon S3 storage may be hosted by the customer on some built-in services. 

Location 4:  Azure Database

SWx stores license, user settings, and website page configuration data in an Azure SQL Database unique to each instance. It interacts with Azure tables to perform functions like controlling access, rendering data reports per setup parameter, etc. Every SOCKETWorx site whether Self-hosted or SaaS connects to a single Azure SQL Server Database instance hosted by ECE.  Each Azure SQL Database is restricted to transact with only Whitelisted Public IP Addresses against company-specific SWx instances.

Data stored within Azure SQL Server::

  • SPECWorx, or CADWorx Pipe Specification Project files data
  • SPECWorx Materials
  • Datasheet Revisions
  • Work Order Metadata
  • Work Order Data Changes
  • PDF Markups and MetaData   
  • MTOWorx Snapshots.
  • CRM Module Data