Welcome to WebmasterWorld Guest from 22.214.171.124
Forum Moderators: ocean10000
The technical support person where they host the website (this was HostPro and is now Interland) tells me the problem is because I use asp on a webserver. He says I will only have good performance if I use a dedicated (not shared) server. He also recommends I use a separate host for my data and convert to SQLserver.
Hey -- this is alot of work and expense for me! Is he handing me a line or is there any truth here?
Should I be looking for a new hosting company, or is it my application?
How large is your database?
With Access, and probably FoxPro, these connections and query objects can linger and eat up memory.
I would ask your host if other sites were just as slow, or just yours.
The speed has nothing to do with running ASP scripts in general, but everything to do with your queries and object creation/deletion.
I was using Access and my site ground to a halt after about 7 users. I switched to mySQL (free) and never had a problem again.
joined:July 19, 2001
There are things you can do to improve performance such as ensuring your database is indexed correctly and optimising your SQL queries.
which, when I run on my local test web server, run quickly.
Although it could be the database, I think it has to do more with the server load than the FoxPro DB. My last host served over 800 accounts. The ASP scripts querying the AccessDB took forever (over 10 seconds sometimes) to load. Like you, when I browsed the pages on the local server everything came up quickly.
Its time to find a new host.
As far as my cleaning up, I do cloae and set to null the recordset and database connections.
Thanks for your ideas so far! I am shopping for a new host, and any suggestions are appreciated.
ODBC does add an additional layer in the connection and can be problematic on shared servers. Use a DSN-Less connection mentioned above "Provider=<yourprovider>;Server=<yourserver>;UID=PWD=;" and tune up the indexes on your database.
Does your production DB change frequently and local one doesn't? If so, you might need to run regular re-indexing jobs to keep fresh.
The servers have plenty of grunt and they're not shared by too many other applications. Of course, it's important to be efficient in your code and database design but it sounds like you're on top of that.
Bottom line: better hosting service required.
I sped things up a bit by removing the ODBC connection and just using a DSN-less connection but other problems started to compound the issue...
So I moved all my accounts to CrystalTech Web Hosting and I haven't had a problem since.