Hi,

I just found an issue with this module.

When you have an Big subscription list (over 30.000 e-mails) and send it or send a test, the module saves the entire e-mail list in 'variable' table in 2 names: newsletter_custom_for_next_cron and newsletter_custom_drafts.

In Drupal 7, Drupal serializes the whole variable table in "cache_bootstrap". With 30k e-mails, both variables can weight up to 16MB. That's a big problem when Drupal unserialize this 16MB.

I just made a patch which creates a new table "newsletter_variables" and saves this two variables in this table, to avoid Drupal to serialize it.

I attach that patch here (for the beta9 version), if you want to show that.

Let me know if I can help you with that.

Thanks

CommentFileSizeAuthor
newsletter.huge_variable.patch7.09 KBisholgueras

Comments

ParisLiakos’s picture

ParisLiakos commented
Status: Active » Closed (duplicate)

I am aware of this problem. but the correct solution would be not to use variables at all..sth that Queue API would solve.thus i am closing this as duplicate of #1869868: Use the Queue API when sending newsletters
Thanks for the patch anyway:)

isholgueras’s picture

isholgueras commented

Upps, I didn't view that issue. Sorry

I will give a try to Queue API.

Thanks

ParisLiakos’s picture

ParisLiakos commented

No problem.i wish i could help rolling the first patch there, but i will review anything for sure..thanks as well