Do you effectively have tested it with 100'000 users?

I'm asking because if you'd use the Automated Job feature the history will be saved at every run of the job with the number of useres defined in the settings.

Also, the queries which are used are quite similar to those in the Members section of the site, so with 100'000 users that section would have performance problems too.

The addon was succesfully tested with 1'200 users, so it would be very interesting to know the behavior with 100'000.

Hi... I did not tested it becouse i'm in production... so i do not feel confortable enought to try to do it becouse I'm afraid that my DB and site could stop working

This is why I asked to have a feature for NOT record detailed results (user level), so I can lauch it and DB will not be affected with tousend of rows

What do you think about it ?
Michele

The mailing will be saved in the DB anyway, means that the DB-table ToessLabNewsLetterSendAddresses will have 100'000 records when you send/prepare that mailing. This is necessary to allow the automated job to work. That DB table is also used to generate the history. There is no separate history table.
As mentioned before, that site has already 100'000 records in the Users and user related tables.

I don't think your site will break when sending a mailing or does it break when you call the Members dashboard page?

If for example you send 5 mails per minute (automated job), only 5 records per minute will be updated in that one DB-table.

Just don't try to send all those mails directly but ONLY as Automated Job! Sending directly will certainly result in an error. But even then this will not break up your entire site but the mailing just won't be sent entirely.

Be sure to choose the right settings under "Newsletter Settings" (/dashboard/newsletter/settings), (see picture attached) and have a chat with your hoster in order to know how many mails per minute/hour are allowed to be sent without being blocked and so be marked as spammer! That is absolutely not what you want to happen to that particular domain!

So personally I'd just try to send a mailing. If you want to be sure that nothing goes wrong, take a DB backup before.

I'd also be interested to know how that add-on is behaving with 100'000 users.

I don't know why your message was hidden here, so I put it in again:

"Yea... I think the best will be to test it once making a full DB backup before...


But even if it works... what will happen assuming to make a mailing each month ?... or you suggest me to clear DB with the "delete" button after each mailing to prevent DB growth ?


Bests

Michele"

That could be a good thing, even though I don't think that a big DB table would be a problem. For example, my User table has 1'211 records in it and has a data length of 240 KB, an index length of 112 KB which gives us a total of 352 KB. So if we multiply this by 100 it gives us an approximative size of 35 MB which isn't too much at all for a mysql DB table.

According to this Stackoverflow question, the limit of a table on a linux system is 4 TB (Terabytes).
http://stackoverflow.com/questions/10436246/mysql-what-is-the-maxim...

Have a good day