| Performance - Working with Large Databases |
It is getting a bit boring with the Northwind and Pubs. Since everybody is using these sample DB for illustration, you cannot really tell which is more powerful in the sense of working with large DB. In this example, we are going to manipulate a 35MB Access DB (with one index - City) and we want to see what kind of performance Tornado can provide. This DB was given to me by a Texas user. Note that the DB has 322,100 records. Pick a big city to return more records like Houston or Dallas will return about 50,000 records. Now, if you are happy with the speed of the retrieval you should not have any doubts about the performance of ASPdb.Net (Tornado). In order to stress the code a bit, the bottom of the returned recordsets are fetched every time even though it is a very expensive operation.
Working with a 35 MB 322,100 Records Access Database
|
<!--T_BigDB.aspx--> <script
language="vb" runat="server"> |
Both ASP-db and ASP-db.Net product use the firehost / datareader mode to retrieve the data records for speed. We have worked with our customers developing application database as large as 50 - 100 MB. Of course the application performance will depends on the implementation as much as the tool. I can only obtain a 35 MB sample database from a user to benchmark the performance.