Best thing would be to have the data in a database, because it would be miliseconds to retrieve the data.
More practically, I would look into building a Progress bar which could show that activity is actually happening. Most users are fine with 3 to 5 second response time as long as they know that something is actually happening.
Thanks for the Response.
I do have a progress bar which greys out the screen while loading...I know 3 or 4 secs for loading data is not a big deal......Actually, the same files are read by a vb program and charts are displayed automatically when a file is updated.
Having data in the database is a overhead as the data is updated in the files every 1 minute during the peak hours and each file has 520 rows * 13 columns of data.
Hmmm. Maybe you should try to break down the problem into its pieces to determine where to make your improvement.
For example, determine how many miliseconds for each part of the process ...
1) read file
2) analyze data
3) draw graphs
4) present results to user
I'm not exactly sure how to capture each one of those statistics because I don't fully understand your application, but you get the idea. Determine which piece of the puzzle is taking the longest and then the folks here can offer you ideas on how to make it better.
Some other points of interest to post would be:
a) what version of IIS are you using
b) what browser is your client using
c) what kind of network connection is between your webserver and client (LAN/WAN), (10/100/1000) MB per second.
d) maybe a simple ping test from the client machine to the webserver could provide insight to a slow network
Good luck. Keep us posted of your progress and solution.