I have just published my reporting application in a report, when I used to generate the same report four times in a row The first one was tried in 185 9 00, while the following people were only taken between 400 and 600 MMS. What is the explanation for this? Can I use it in any way to make my application faster? The reporting module runs on the server and waits for the user to click on "print report."
Never seen your app, my guess is that the biggest impact will be that your database server caches the data you ask. It loads the disk into disk and into memory, and is doing nothing better with that memory, it leaves there next time comes with the query, the database does not have to go to disk, it is still memory Is in.
The obvious and simple way to take advantage of this is to run a "fake" query before your users get loose on the system; This would mean that you wait 1800 ms and your users get 400 sweets. Unfortunately, this will work only when all questions are the same, that is, if all requests for the same report are different reports and different data, the cache will be flown for different data and New results will take longer to load. In essence: If you always have the same question, you can give a really quick answer, but then you will never present something new.
Comments
Post a Comment