Menu
You check the website before launching a marketing campaign. Pages open quickly, images are optimized, and the speed tests look fine. But those checks don’t show what happens when several operations need the server’s attention at once.
Once the campaign starts bringing in traffic, customers begin browsing products and placing orders. Meanwhile, someone on your team starts importing a subscriber list, and an automated catalog update is still running. Soon, a few customers report that their checkout requests aren’t going through.
The pages themselves still load without trouble. But orders need to be processed, payments confirmed, and customer details recorded. With the import and catalog update already running, those requests may end up waiting for server resources that aren’t immediately available.
Advertisment
Several editors have administrator access to the CMS. One of them starts updating categories across hundreds of articles while other team members continue working on the site. Nobody checks whether another large operation is already running.
Articles begin taking longer to save. The admin dashboard feels unusually slow, then returns to normal once the bulk update finishes.
Use a shared editorial calendar to coordinate bulk edits and index rebuilds. Plan these operations for quieter hours and make sure they don’t overlap. One administrator should coordinate those changes while other editors keep their regular publishing permissions.
For a larger update, run it on staging first. You’ll get an idea of how long the operation takes before scheduling it on the live site.
A sales manager starts exporting six months of transaction history from the website’s database. The file contains thousands of records, and the export takes longer than expected. Other database operations may also slow down while it’s running.
There are two ways to keep these operations from interfering with regular website activity:
Advertisment
You open the server logs after noticing several 503 errors. The website wasn’t receiving an unusual amount of traffic, but some requests still failed. A closer look shows that all available PHP workers were occupied when those errors occurred.
It’s tempting to increase the worker count immediately. But every additional process needs memory, and the server may already be using most of what’s available.
Check how much memory the server has left when all workers are busy. If there’s enough room, increasing their number may help. If memory is already running low, adding more workers could cause further problems. Find out what’s using it before adjusting the limit.
The next challenge is keeping up with the website’s growth. As more customers use the site, the demands on its web hosting environment increase, with the server handling more requests throughout the day.
The first signs may appear in request processing times. Peak traffic may remain fairly consistent, but requests start taking longer to complete than they did a few months ago. Some operations that once finished quickly may now continue running well into the next busy period.
Rather than waiting for another round of performance problems, use those trends to plan ahead:
Some website functions rely on external APIs for payments, shipping calculations, or other services. The problem begins when those services respond slowly. The website has to wait for information it cannot retrieve or process on its own.
A slow response from an external API can delay more than one operation. Requests that depend on the external service may remain open longer than expected. If several arrive together, the delays can spread to other parts of the website that have nothing to do with that service.
To keep external services from affecting the rest of the website:
The same attention to performance applies when choosing third-party tools. Lightweight services such as Plausible, discussed in startups that solved problems larger tech companies overlooked, show why the software connected to a website deserves attention too.
Advertisment
Balancing server concurrency means deciding how different operations share the available resources. Customer requests need to be handled on time, but the website also has internal work that can’t simply be ignored.
The problems begin when these activities aren’t properly coordinated or the hosting environment no longer matches the demands of the website. More processing power can sometimes help, but the real improvement comes from making better use of what’s already available.
When that balance is right, the business doesn’t have to interrupt its own work to keep the website running. Content can be updated, data processed, and new services introduced while customers continue using the site.
Advertisment
Pin it for later!
If you found this post useful you might like to read these post about Graphic Design Inspiration.
Advertisment
If you like this post share it on your social media!
You Might Be Interested On These Articles
Advertisment
Latest Post
Want to make your Business Grow with Creative design?
Advertisment
Advertisment
Best Resources For Graphic Designers
