Xinet

"It's a great pragmatic solution that delivers real results."

The Marketing Store, Steve Dennis



 

"Our teams and our partners have access to this 24/7 so they can now download what they need at any time. It saves days and shipping fees, customs problems, everything."

Young & Rubicam, Kathy Dzielak



 

"In one department alone, where we just catalog images, we will save 4,000 man hours by next year."

Macy's, Shani Schechter



 

"It's probably one of the best moves we made, buying WebNative. It's one of those things, that if I could, I would keep it a secret from our competitors."

Zebra, Paul Samuels


Request a Demo!


Xinet WebNative Suite Scales to Fit Your Needs
Guidelines for selecting a server    Download Guidelines


Xinet® WebNative® Suite is a scalable software solution for organizations of every size. Whether yours is a large enterprise operation with offices around the globe, or a small boutique business offering specialized, local services—WebNative Suite scales to meet your needs.

Select a WebNative Suite Server

Many factors must be taken into consideration when selecting hardware to run WebNative Suite efficiently in your environment. The size of your business, the number of local and remote users who will access the system, the amount of content to be managed, and the frequency with which content changes are some of these factors.

WebNative Suite servers are tasked with numerous responsibilities—such as file serving, print spooling, PostScript optimization, website hosting, and tracking of processes throughout the system.

Our Authorized Xinet Integrators (AXIs) can help you clarify your needs based on their experience with customers of all sizes, in locations around the world. Before you meet with your AXI to determine your unique hardware requirements, consider the following points as a basis for your purchasing decisions.


CPU Consumption

Copying files to the server, creating print output, and the operating system itself are the largest CPU consumers. Consider the following information about CPU usage on a WebNative Suite server:

 
  • UNIX and Windows based operating systems optimize CPU usage.
  • Previews are immediately generated when a supported image type is copied to a WebNative Suite server volume that has been configured to generate a preview for that image type.
  • PDF image replacement and PostScript image replacement tasks use CPU during the actual image replacement process.
  • Generating key frames for movies on the WebNative Suite server is CPU intensive (one CPU).
  • Compressing files prior to downloading them from the web uses CPU.
  • SQL queries, especially large searches, cause some CPU consumption.
  • The AFP server’s concurrent user load has a slight impact on CPU usage; the specific CPU usage depends on exactly what each user is doing over the AFP connection at any given time. More AFP connected users equates to more CPU load.
  • Many RAM consuming activities listed below also lead to CPU consumption.
    		•

     

    RAM Consumption

    Some organizations look to reduce server hardware costs by purchasing less RAM. Xinet recommends purchasing as much RAM as possible, since UNIX and Windows operating systems are set up to use any available RAM to optimize server performance. Consider the following information about RAM usage on a WebNative Suite server:

     
  • UNIX and Windows based operating systems optimize RAM usage, including using some RAM to cache file system contents.
  • The SQL database functions best if the entire table size can be cached in RAM.
  • During searches, extra RAM is temporarily needed to build optimized SQL queries on the fly and to cache hits before they are returned.
  • Indexing heavily searched tables speeds up searching, and indexed tables are larger and function best if cached in RAM.
  • The PDF generator accesses RAM sporadically to function optimally.
  • The AFP server’s concurrent user load has a slight impact on RAM usage; the specific RAM usage depends on exactly what each user is doing over
    the AFP connection at any given time. More AFP connected users equates to more RAM load.
  • The Apache web server will consume some RAM.