Faster Processing 3

[AgentM]

I am using ASP with Access 97, PWS running on a windows 98 machine.

My asp pages do a lot of Database processing. Like looking up queries in Access, update etc.The processing is slow

Will adding more RAM to the machine make it faster?

Or do I need to start coding in VB then use ActiveX dll's.

Any ideas???

 

[vasah20]

Do both. Max out the RAM to give it more space to operate in, and code in COM so that you run compiled code (which is generally faster)

 

[AgentM]

Thank you for the quick reponse...

In COM can I create two different objects for two different Dll's?

 

[wushutwist]

Yes about the COM question. Also to improve speed switch to a real RDBMS like SQL Server or Oracle. Even MySQL would be better than Access and it is free.

Adding more RAM may or may not make it faster. It depends on if your machine is consisently swapping to the hard disk. If so then Yes. If not then more RAM won't do anything for you. Wushutwist

 

[AgentM]

Thank you,
I cannot go for Oracle or SQL Server
MYSQL hmmmmm....

Roshan

 

[jasonsalas]

The COM suggestion would definetly help...but also try this...if you're not doing it already.

Use stored procedures to generate your information, as opposed to just extracting data from a table. For queries requiring calculations, this really helps...you have Access perform the calculations itself and then your ASP just is responsible for outputting the result.

It seems kind of silly to set up an entire query just to retrieve the same info you could pull from a table, but it does make a difference.

Your Web server will note the query the first time the script fires the query and for each subsequent time after that, try to use the fatest-route method of extracting your data. Kind of like an ASP method of caching information.

In SQL Server, such methods known as stored procedures, but in Access lingo they're called both "SPs" and just "queries".

While not mind-blowing in terms of performancem, it does reduce processing load on the server and is beneficial in times of high traffic.

I've done this myself for a site I set up to tarck a local football league statistics, and it works out.

ASP.NET apparently alleviates this problem altogether in terms of performance, but this is a little gem that'll do you some good.