It is just a trait of MicroSnot SQL Server. It could also be related to the amount of bandwidth available to access the database. The capability of the hosting server, including number of spindles that the database is spread across. But more likely the scalability of the actual Web Server to deliver requests at peak times. MySQL ; Postgres ; Oracle etc.. can all produce similar results. The use of a Post RDBMS database engine would certainly reduce the issue, but would require a large amount of effort to implement. The volume of data will / can obviously impact upon the amount of time that a web page is displayed, no matter how clever the indexing mechanism.
|
|