-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very high memory usage when migrating measurable #41
Comments
Could possibly help to change usages of foreach like here: |
@Starker3 I have the same issues using this plugin migrating a measurable. I increased the ram of the machine just for the migration to 16GB but it still fails. It fails with two different outcomes.
All this when trying to migrate a measurable with "4241620 visits". As it stands it seems the only way around this is to increase the RAM of the machine to extreme amounts , then migrate and lower ram back down. |
UPDATE: After increasing RAM to 32GB i managed to migrate the site in 2h13mins. |
We had another user that had a similar experience as report in #38
However, in this case there was at least an error that was output:
ERROR [2022-08-01 11:12:19] 348340 Fatal error encountered: /var/www/matomo/libs/Zend/Db/Statement/Pdo.php(292): Allowed memory of 6442450944 bytes exhausted (tried to allocate 8192 bytes) [Query: , CLI mode: 1]
The user needed to increase the allowed memory to all available memory (AFAIK 16gb at least) in order for the migration to complete.
I asked the user to send us the size of the log_ tables, since it seems that there is an array created and held in memory for
LogActionMigration
which might be kept for the entire Migration.But the size of the tables for this database are not very large, so the used memory seems to be quite excessive:
The text was updated successfully, but these errors were encountered: