Aussie AI
Online Architecture Optimization
-
Book Excerpt from "Generative AI in C++"
-
by David Spuler, Ph.D.
Online Architecture Optimization
The AI engine and its model are only part of your production architecture. An online website version needs a backend server that receives user requests, marshals them to an API, that then sends them off to the AI engine. The AI engine shouldn't be running on the same tech as your basic server, so the requests are sent remotely whether it's your own AI engine or a commercial API wrapper architecture.
Website Optimization: There's a whole bag of jobs needed to optimize the user response for a website, and most of that is well-known and unrelated to AI. Some of the issues include:
- Apache versus Nginx
- DNS speed (DIY vs use a commercial provider)
- Image sizes (i.e. low-resolution images)
- Script sizes (e.g. minifying JavaScript)
- HTML page sizes
- File cache settings
- Etags
- SSL/HTTPS certificates (e.g. LetsEncrypt is free)
- Third-party scripts (e.g. Google AdSense, Google Analytics)
- Cookie management (or like Mater: “to not to”)
Some of the broader issues include:
- User account management
- CDN usage
- Analytics
- Ad serving scripts
- Cloud hosting servers (GPU and non-GPU)
- Multi-server management
Having a website run small and fast is a whole tech discipline in itself. This book does not cover many of these non-AI-specific website optimization issues in detail.
• Next: • Up: Table of Contents |
The new AI programming book by Aussie AI co-founders:
Get your copy from Amazon: Generative AI in C++ |