2

In the php.net site, they say that those who use mysql4.1 next to php5 or higher is required to use extremely "MYSQLI_" instead of "MYSQL_."

He wanted to know just one thing, it influences the performance of the site, several problems with site is down due to the database (this on any server).

Already using various solutions. For example, CACHE HTML pages.

But my doubt is really about on MYSQLI_ *, when we use it, she connects to the server and the specified DataBase. According to the php.net site is mysql mysqli improved and optimized mysql4.1 +.

I wonder if the traffic with a large MySQLi give better performance to the site.

PS.: I know the difference "mysqli" and "mysql", taking into consideration the PHP programming and structuring of MYSQL4.1+ (which has new types of columns). What I want to know is on multiple connections.

This question is about performance, thanks

Cœur
  • 37,241
  • 25
  • 195
  • 267
Protomen
  • 9,471
  • 9
  • 57
  • 124
  • Please, don't use `mysql_*` functions for new code. They are no longer maintained and the community has begun the [deprecation process](http://goo.gl/KJveJ). See the [**red box**](http://goo.gl/GPmFd)? Instead you should learn about [prepared statements](http://goo.gl/vn8zQ) and use either [PDO](http://php.net/pdo) or [MySQLi](http://php.net/mysqli). If you can't decide, [this article](http://goo.gl/3gqF9) will help to choose. If you care to learn, [here is a good PDO tutorial](http://goo.gl/vFWnC). – PeeHaa Jul 12 '12 at 07:45
  • possible duplicate of [Why shouldn't I use mysql\_\* functions in PHP?](http://stackoverflow.com/questions/12859942/why-shouldnt-i-use-mysql-functions-in-php) – ljk321 May 05 '15 at 02:51

4 Answers4

3

You should read this:

http://blog.secaserver.com/2011/07/php-driver-mysql-mysqli-pdo-mysql/

mysqli provides better performance and increased functionality and as Evert said, it is especially noticeable if you use mysqlnd.

Max Hudson
  • 9,961
  • 14
  • 57
  • 107
2

A common comment here at StackOveflow whenever we see code using mysql_* functions should answer your question:

Please, don't use mysql_* functions for new code. They are no longer maintained and the community has begun the deprecation process. See the red box? Instead you should learn about prepared statements and use either PDO or MySQLi. If you can't decide, this article will help to choose. If you care to learn, here is good PDO tutorial.

John Conde
  • 217,595
  • 99
  • 455
  • 496
1

Yes, MySQLi could give better performance to your site. You can use persistent connections, which basically share the same idea of the well known connection pooling, but while the connection pooling is used in java development mostly(usually performed directly by the webserver, e.g. Apache-Tomcat), persistent connections are managed by MySQL and PHP.

Besides, MySQLi could help you to secure your queries, by adopting prepared statements.

Mysqli extension provides built-in cleanup handling code, which includes:

  • Rollback active transactions

  • Close prepared statements (always happens with PHP)

  • Close and drop temporary tables

  • Unlock tables

  • Reset session variables

  • Close handler

  • Release locks acquired with GET_LOCK()

All these features could help you to give better performance and security as well.

For more informations, you can refer to:

http://php.net/manual/en/mysqli.persistconns.php

A_nto2
  • 1,106
  • 7
  • 16
0

The mysql_ functions are no longer maintained and deprecated. The mysqli_ functions will perform better, especially if you use the mysqlnd (native driver).

Stop using deprecated API's!

Evert
  • 93,428
  • 18
  • 118
  • 189
  • I understand, just wanted to know if there are advantages over the server. Could I confirm this? – Protomen Jul 11 '12 at 20:26
  • 1
    Yes they will improve, provided you use mysqlnd. However, unless you are absolutely massive size these benefits will be small for you. It's much, much more likely you need to optimize your database and code. Don't expect a big change when you start using mysqli – Evert Jul 11 '12 at 20:30