Slow response using ODBC/VFP



Hi,

Am currently using a MySql database on my web server that I access using the
Php MySql commands. The performance is great.

As this database starts its life as a Foxpro one, I have tried to access the
original data using ODBC and the VFP driver.

In essence this works quite well until I request a complex procedure and
then it all falls apart.

The same procedure that talkes MySql 1 second to complete, times out at 60
seconds with only partial data returned using ODBC/VFP. During this time the
CPU maxes out to 100% utilisation. When using MySql it gets up to about 3%
for the whole 1 second.

The databases are the same size, are on the same WinXp server (as MySql
Server, Apache Server and Php) and the same Php code is used, albeit
slightly changed for the differences between MySql and ODBC.

Can anyone suggest to me why ODBC/VFP is horribly slow while MySql is a
rocket?

Thanks in hope.

Regards,

John Clarke


.



Relevant Pages

  • Re: Trying to build a database driven website
    ... The database is stored on a remote server which all ... I've installed MySQL, PHP and Apache on ... My biggest problem is how to connect to the database on ...
    (comp.lang.php)
  • Re: Trying to build a database driven website
    ... The database is stored on a remote server which all ... I've installed MySQL, PHP and Apache on ... My biggest problem is how to connect to the database on ...
    (comp.lang.php)
  • Re: hitting the limits
    ... relatively straight forward MySql database. ... 10K visitors a month and an 80Mb database are nothing. ... heavily loaded server. ... But the connection will hang around until the garbage ...
    (comp.lang.php)
  • Re: Database connection error (re-post)
    ... MySQL is a database server, it is not a desktop database like Access, you have to work with directly ... FrontPage Resources, WebCircle, MS KB Quick Links, etc. ...
    (microsoft.public.frontpage.client)
  • Re: Executing PHP files on remote web server
    ... We have a commercial web host servicing our external clients, but we don't want to move the entire app and database to the web host because a lot of the data is sensitive. ... By loading the non-sensitive data into the web host's MySQL tables, our external clients can see their reports on the web. ... our web host put a firewall on the MySQL database so we can't insert data into the remote tables directly from the PHP pages running on our own web server. ...
    (comp.lang.php)