Question about your example

  • Resolved cvrle77

    (@cvrle77)


    2 years, 11 months ago

    In a DigitalOcean droplet with 2 Gb of RAM and 2vCPU, it can send around 13.801 notifications in 56 seconds

    It seems you forgot to mention, did that notification on your test had image or it was textual notification, and what size the image was if there was any, because it seems that image is making the biggest impact on server, when sending notifications. For example, I have 2cpu 4 gigs droplet on cloud, and I can’t use half of those settings without crashing my entire server, so I have to use less than 1/4 of those settings. Batch size of 3000, and PFS of 30, memory 1G, MET 300 works…

    But, if I send manual notification, and reupload image on some image host, like imgur, there’s no serious spike in CPU usage.

Viewing 1 replies (of 1 total)
  • Plugin Author Perfecty

    (@perfecty)

    Have in mind the notification payload the plugin sends contains only a json string, not the image content. So, no matter the size or resolution of the image, the payload is only made of json text.

    Now, when you send a notification, all your user’s browsers receive the json payload and download the image url it contains to display it in the OS tray, and that sudden spike of image requests overload your website. In that case you might consider using a CDN that caches the images, like CloudFare.

    But for sure it’s not the plugin’s fault :), and I’m happy you’re having so much users, keep growing!

Viewing 1 replies (of 1 total)
  • The topic ‘Question about your example’ is closed to new replies.