5 ms·
friendly reminder: 400k is an apertif for a competently configured production postfix server. its about 14 seconds of mail, and about 8 seconds optimized at hw
by nimbius 4y ago
friendly reminder: 400k is an apertif for a competently configured production postfix server. its about 14 seconds of mail, and about 8 seconds optimized at hw and filesystem level.
the real issue here is shitty projects from shitty companies.
- emilyst 4y agooh.
- kaetemi 4y agoA lot of developers seem to underestimate how fast well-written software can process things...
- chupasaurus 4y agoYep, the mail bodies would be cached out while the rest is just the addresses in queues.
- deleted 4y ago[deleted]
- wonderbore 4y agoYes but that’s on top of what GitHub is already sending, plus it must be multiplied by the number of comments left on top of that. It feels like 35 straight minutes of 100% usage isn’t great on any system. It presumably sent 61 million emails.
- cortesoft 4y ago> Yes but that’s on top of what GitHub is already sending When you send at the volume someone like GitHub sends, you will always see peaks and valleys in your sending patterns that are much larger than 400k. It might cause an issue if they were already under peak load, but even then it would just take a bit longer.
- EugeneOZ 4y agoGitHub can afford more than one computer to send their emails.
- withinboredom 4y agoWhere I work, we send over a billion emails a month (blog subscriptions) and 400k is not even a blip.