In many server configurations, a user sends an HTTP request, the server crunches data, often sending requests of its own to an SQL server, then it sends the data over the wire. Slashdot encourages users, “Optimize PHP and Accelerate Apache.” Some of the advice in this article is meant to be humorous, but one nugget is quite powerful. Move the business logic and the database client-side. This has an amazing effect on server resources.
Ajax Minimizes Traffic
Maintaining a Live Connection Serves Data Faster
Many servers today maintain a connection to the browser, even after the page has been served. This saves resources. First, the HTTP protocol requires several bytes when first established, so keeping a live connection minimizes network traffic. Second, building up and tearing down connections also takes resources. Keeping the connection open until the user session ends preserves these resources.
Uploading Data Keeps Things Moving
One powerful feature Google has implemented with its Google Reader service is the ability to download up to 2000 articles for later viewing. This is an excellent approach because: The user can view the information offline (while commuting), but even when online, the user experience is incredibly fast because the data is local. Of course, this service is based on information, so users have to come back for updates.
Work Smarter, Not Harder
Users are running fast systems, even iPads and iPhones are fast enough. Letting the user computer do the work turns servers into distributed systems, which are well known for their performance. This being said, ensuring that servers have enough resources to begin with is crucial. One big requirement is ram. If you’re interested in getting the most from your PowerEdge or ProLiant server, check us out!