Performance issue with OneSignal (slow requests / curl_exec blocking)

Subject: Performance issue with OneSignal (slow requests / curl_exec blocking)

Message:

Hello,

I’m trying to confirm if other Sngine users are experiencing performance issues related to OneSignal push notifications.

On my setup, I noticed that every user action (messages, comments, reactions) triggers:

post_notification()
→ onesignal_notification()
→ curl_exec()

The problem is that curl_exec() is blocking the request.
If OneSignal API is slow, the whole page request becomes slow.

🔎 How to check on your server (SSH)

If you have SSH access, you can verify this easily:

tail -f /var/www/vhosts/system/YOURDOMAIN/logs/php-slow.log

Then perform actions on your site:

• send a message
• post a comment
• react to a post

If you see entries like:

curl_exec()
onesignal_notification()
includes/ajax/posts/comment.php
includes/ajax/chat/post.php
includes/ajax/posts/reaction.php

→ it means OneSignal is blocking your PHP requests.

⚠️ Symptoms

• Messages take time to send
• Comments “loading” delay
• Users click multiple times → duplicate actions
• High PHP-FPM usage

❓ Question

Do you experience the same behavior?

If yes:

• Did you find a solution?
• Are you using async/queue system for notifications?

💡 Suggestion

This should ideally be handled asynchronously (cron / queue), not inside the main request.

Thanks 👍