<div>
<div class="content wysiwyg-content">
Recently we have had a major problem where php pages on site, which contain numerous mysql database executions, have slowed down and conked out completely because they exceed the maximum of 30 seconds to execute. <br />
<br />
This may be a major program flaw, but the pages were originally programmed so that each user accessed the mysql database with their own user id and password, the same as used to login to our site. However, I have read that have to sort through all this permission/privilege/passw<wbr />ord &quot;overhead&quot; is very resource-consuming. If the number of such users with privilege and passwords for access is nearly 2,000, does this basically explain the major slowdowns and exceeding 30 seconds for php scripts w. a lot of mysql?<br />
<br />
If we go back to having one access code/password that all users use encrypted and secured, of course), would that basically solve this problem?
</div>
</div>


Recently we have had a major problem where php pages on site, which contain numerous mysql database executions, have slowed down and conked out completely because they exceed the maximum of 30 seconds to execute. 

This may be a major program flaw, but the pages were originally programmed so that each user accessed the mysql database with their own user id and password, the same as used to login to our site. However, I have read that have to sort through all this permission/privilege/password "overhead" is very resource-consuming. If the number of such users with privilege and passwords for access is nearly 2,000, does this basically explain the major slowdowns and exceeding 30 seconds for php scripts w. a lot of mysql?

If we go back to having one access code/password that all users use encrypted and secured, of course), would that basically solve this problem?

Do hundreds of individual mysql privileges/passwords slow down execution big time?

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.