Reply to thread

Message

I'm not a MySQL expert. I would guess the answer is "no"... but what is the point of your question? If we knew that there is or was something wrong with the TV Server database that was causing the slow start then it makes sense. However, we don't know that there is something wrong with the TV Server database, or that the TV Server database has anything to do with the MySQL slowness. In other words, it seems like you're assuming that the TV Server database is somehow causing the problem, but we don't actually have any proof for that.

I'm sorry I don't think there is enough evidence to make that statement either.

If you had repeatedly stopped and started MySQL independently after performing the change, and it started quickly each time... and then you started MP/TV Server and MySQL reverted to the slow behaviour... that would imply that MP or TV Server was doing something that messed with MySQL.

This reinforces my point: it seems like something is wrong with the MySQL "engine", independent of the databases, database contents etc.

Those log files are not very verbose. You should be able to set the log level/verbosity lower so that you get more detail. Additionally I think there are at least InnoDB engine logs that should also be checked.

Side question: how large are the log files? If they're very large, it may be a good idea to purge them.

It isn't possible to just replace MySQL with SQLite without additional changes.

<blockquote data-quote="mm1352000" data-source="post: 1148172" data-attributes="member: 82144">I'm not a MySQL expert. I would guess the answer is &quot;no&quot;... but what is the point of your question? If we knew that there is or was something wrong with the TV Server database that was causing the slow start then it makes sense. However, we don't know that there is something wrong with the TV Server database, or that the TV Server database has anything to do with the MySQL slowness. In other words, it seems like you're assuming that the TV Server database is somehow causing the problem, but we don't actually have any proof for that.I'm sorry I don't think there is enough evidence to make that statement either.If you had repeatedly stopped and started MySQL independently after performing the change, and it started quickly each time... and then you started MP/TV Server and MySQL reverted to the slow behaviour... that would imply that MP or TV Server was doing something that messed with MySQL.This reinforces my point: it seems like something is wrong with the MySQL &quot;engine&quot;, independent of the databases, database contents etc.Those log files are not very verbose. You should be able to set the log level/verbosity lower so that you get more detail. Additionally I think there are at least InnoDB engine logs that should also be checked.Side question: how large are the log files? If they're very large, it may be a good idea to purge them.It isn't possible to just replace MySQL with SQLite without additional changes.</blockquote>

[QUOTE="mm1352000, post: 1148172, member: 82144"] I'm not a MySQL expert. I would [B]guess[/B] the answer is "no"... but what is the point of your question? If we knew that there is or was something wrong with the TV Server database that was causing the slow start then it makes sense. However, we don't know that there is something wrong with the TV Server database, or that the TV Server database has anything to do with the MySQL slowness. In other words, it seems like you're assuming that the TV Server database is somehow causing the problem, but we don't actually have any proof for that. I'm sorry I don't think there is enough evidence to make that statement either. If you had [B]repeatedly[/B] stopped and started MySQL independently after performing the change, and it started quickly each time... and then you started MP/TV Server and MySQL reverted to the slow behaviour... [I]that[/I] would imply that MP or TV Server was doing something that messed with MySQL. This reinforces my point: it seems like something is wrong with the MySQL "engine", independent of the databases, database contents etc. Those log files are not very verbose. You should be able to set the log level/verbosity lower so that you get more detail. Additionally I think there are at least InnoDB engine logs that should also be checked. Side question: how large are the log files? If they're very large, it may be a good idea to purge them. It isn't possible to just replace MySQL with SQLite without additional changes. [/QUOTE]