April 18, 2011
System performance is a general term. It means, how the system (hardware, software or both) is doing under some specified conditions. Or how best can system performs under real load conditions. An appropriate measure for the performance should be chosen based on the most valuable aspect given any situation. There isn’t a single common parameter that fits all situations.
One of the most commonly used parameters for measuring performance is the number of transactions the system performs in one second or, ‘transactions/sec’. This simply counts the number of operations a system can do in one second. This parameter is all right if it is required that the system deliver maximum number of transactions.
Another frequently used parameter is – how long does a specified operation take to complete. This is ‘inverse’ of the previous parameter. Here the interest is in the average time (say in milliseconds) taken to complete a single transaction. This may be of interest if one wants a measure of how FAST the system serves users.
There are other performance parameters as well. For example, how efficient the code is (especially, code which does computation), then one is interested in looking at the number of cpu cycles spent in doing transactions every second or, ‘transactions/sec/cpu’. An efficient code will deliver greater transactions per second while using less cpu.
If the interest is in the measure of raw data performance – written or read from the disk then the appropriate parameter is the number of blocks written/read form the disk. If one is studying the performance of data-base then one may want to look at how many SQL operations (or scripts) are executed per second.
For a web-server, it could be the time taken to load the pages from multiple users.
The measure of performance should capture the quality that is being sought in the system. The performance numbers or claims may prove misleading simply because one is not using the correct measure of performance. It is thus very important to choose the correct measure of system performance.
April 12, 2011
In any system under performance consideration, there are 3 important timescales.
- The timescale at which the CPU works
- The timescale at which the Memory can be accessed
- The timescale at which data can be stored on disk
These three have widely different timescales in a traditional computer setup. CPU runs at nano second resolution, memory at micro-second and Disks at milli-second.
This makes it difficult to estimate the true efficiency of code. Because, the rate at which the instructions can be processed also now depends on the rate at which the memory is accessed and the disk is utilized. Hence, to truly measure the code efficiency one needs to make sure that the disk response times do not play a major role in the flow of instructions. In other words on e should take care of removing the IO bottlenecks before analyzing the performance of code.
In presence of strong influence of disk IOs the measurements will be biased by the characteristics of the storage system. The order of magnitude difference between the response times of disks and memory and memory and CPU makes it even more difficult to remove the IO bottleneck. While the CPUs have become faster in the last few years and there are now CPUs with multiple cores the memory and disk access speeds haven’t kept pace. As a result the contrast between the response times of CPU, Memory and Storage has widened.
April 9, 2011
Cloud computing is now synonymous with Flexible Provisioning and Scale. Find out below if you are taking full advantage of cloud computing.
The As Is deployment – lowest adoption cost, reasonable benefits:
Move the server application “as is” to a cloud server. This is nothing but a co-located server, at Amazon for example. The provisioning and maintenance of the application is still a self driven task.
The win is in the dynamic on demand provisioning. Easy to compute the ROI here. Let us say that your application needs to be available all year round – but cater to seasonal demands. Say it costs $400 to host your application to cater to peak demand. You would end up paying 12*400 = $4800 per annum to keep your application up. Most of the time it would be under utilized. Cloud computing has made it really simple to change your compute capacity as easily as setting a reminder in your out look calender. With amazon or google, you could just log into the admin panel and say that you need additional resources only on certain dates. At the end of the month you get billed for the amount of resources you actually consume.
The Managed RDBMS deployment – reasonably low adoption cost, reasonable benefits:
A lot of work has to be done to ensure that the application is available. i.e. a replication strategy and policy to keep the database available. This is still a lot of effort and money. The alternative is a managed RDBMS, where the provider (amazon or google) manages the database. They worry about keeping the data safe from being lost. Much harder to do the ROI here – as the time spent in managing this would have to be offset against opportunity costs. Note that there would be some amount of code restructuring (not a lot) to get this going. An example of this is the Amazon MySQL RDS. At the time of writing, google is yet to announce the availability of their hosted sql service.
The Application Rewrite – highest adoption cost, highest benefits (arguably)
If your goal is to write an application which scales very well then you should consider a complete application rewrite to take advantage of the storage APIs. Hosted RDBMS is still a single machine (or a cluster) running a database server – with bottlenecks – be it memory, cpu, networ or disk.
Cloud computing offers storage APIs to access and manage data unlike traditional methods of file or rdbms storage. Because of the underlying architectural differences, cloud datastore offers better scalability -
April 8, 2011
Solid state device threatens to challenge and change existing computing paradigms.
While traditional disk access times are of the order of a few milli seconds, ssd access times are under 100 micro seconds for reads and writes respectively. Speeding up by a factor of 100. And that is significant.
Operating system components have evolved over the last 4 decades at a much slower speed. For an enterprise platform like IBM AIX or HPUX it takes A few years (my guess is a minimum 6) to push a new technology. The cycle is as follows – a new hardware technology is invented. OS vendors take a few years to adopt and evangelize. Enterprise customers longer to test, adopt and deploy.
SSD promises to deliver better performance by lowering IO latency and increasing throughput. File systems have evolved to do the same. Specialized caches have been invented to speed up performance. For example directory name lookup cache, page cache, inode cache, large directory cache, buffer cache and so on.
Quite a lot of focus is on being clever with reads and writes of application data. Engineers go to great extents to squeeze the last bit of performance out of the system. Sadly performance is not a main consideration during implementation (functionality is) and is often times applied as an afterthought.
The result is hacks rather than elegant solutions to performance issues.
Coming back to SSDs – a large portion of the file system implementation has to be re looked at and parts of it have to be thrown away completely. Especially true when complete filesystems are laid out on SSD. We need to look at how filesystems can take advantage of SSDs.
April 7, 2011
Most file-systems have intelligent caching policies. The policies are designed to increase the throughput and decrease IO latency rates thereby providing faster service times to the users and applications. Based on the nature of the workload, appropriate caching policies can be set to achieve maximum cache-hit rates.
However, this works as long as there is enough memory to store revisited pages. Once the number of pages cached exceeds the set memory limit, the file-system decides to reclaim space by flushing older pages to the storage. If flushing is not done frequently, a lot of data may suddenly be dumped on the disk leading to storage bottleneck.
Depending on storage bandwidth, flushing large amount of file-system data can lead to very large service times for the users or the application. For all-round good performance one thus needs to also look at how frequently and how much of data is flushed to the storage. Just like caching policies should take into account the nature of workload, flushing policies should take into account the nature of storage and storage i/o bandwidths.
A good sustained file-system performance is possible only when both, caching and flushing, policies are set optimally.
April 5, 2011
It is important to understand if the performance problem is due to the latency or the bandwidth. These two are very different phenomena but they may have similar looking outcomes.
In case of latency a transaction or an IO is taking a long time to complete. The question would be: is the time taken to complete the transaction reasonable or is it longer than what is desired. In many cases, the latency is unavoidable but one can use several techniques such as filling the pipeline or sending the IO in blocks. And storing in the buffer to hide the delay due to latency.
Bandwidth on the other hand, sometimes the performance is low because either the bandwidth is not utilized fully or it is inadequate. Even in this case one would observe low performance. To improve the performance which is limited by bandwidth, one has to understand and match the bandwidth of various devices along the IO path. Several techniques can be used to optimize the bandwidth. Such as load balancing, multi path and adaptively adjusting the parameters.