Hall of Fame

[harrygian]

Hello,
After upgrading to version 4.X the website phpvibe become very very slow.
every thing is working great but so slow, in the logs no errors.
the videos is more than 1 million however before the upgrading the website were running fast

would you please help me ?

[PHPVibe A.]

If you have more than 1 million videos the database must be fully overheated when making a simple query in the video table.
There is no big difference between 3.x and 4.x in that area, actually 4.x is faster than 3.x since it has the full cache, this is one of the main improvements, in speed.
But, on 1 million videos, not sure what to say, basically the queries are the same, the sql class is the same.

You should periodically run an optimize database and check your database settings, maybe a google a tutorial on how to configure the sql server for large data storages.

[harrygian]

the tables already optimized , the mysql server configuration is already set for the large databases.
I think the problem with a poor queries structure on the website frontend because the database is fast on the backend admin area and I can manage the videos very fast
while sing the top command
I see that
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
45552 mysql 20 0 2193444 265356 11260 S 106.5 0.8 45:08.95 mysqld
and sometimes the CPU usage got more than this value it some times reaches 650% so the queries is overload and eat resources

I would like a solution for that please   

[PHPVibe A.]

For which query? Which page? I can't tell you like this, I monitor 4 servers with over 34 PHPVibe websites on them...and I don't see anything remotely similar.
All that happen after the 4 upgrade was that the load was decreased.

[PHPVibe A.]

One other question is: is it upgraded correctly? Since 3.x had a problem with "guess next" which was fixed with an index on 4

[shahidashraf78]

HI, I'm also facing slow response on loading home page after upgrading 3.6 to 4.22, I'm having almost 45000 videos. what could be the issue..

[PHPVibe A.]

Hi! This is something your browser console and your server (error logs) can tell you...not us, we can't guess what's going on.